|
That so often depends on how they're written. Of course it would help if microsoft would document the designer API better
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
Everything will be fine as soon as .Net Core 3.0 will be released, it's a magic bullet that will make all your pains go away !
|
|
|
|
|
What? Instead of shooting myself in the foot I can now shoot myself in the head?
|
|
|
|
|
Quote: An angel's smile is what you sell
You promise me heaven, then put me through hell
Chains of love got a hold on me
When passion's a prison, you can't break free
Oh, you're a loaded gun, yeah
Oh, there's nowhere to run
No one can save me
The damage is done
|
|
|
|
|
I could crash the WPF designer just by looking at it.
|
|
|
|
|
|
Are you really that ugly?  
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
My C#/WPF app uses some *.h files shared with our Windows services which are written in C++. These files are compiled into a 64-bit assembly. Of course, Visual Studio and the WPF designer are 32-bit applications, so they can't load 64-bit code. The WPF preview function therefore doesn't work. I used the vaunted designer for its XML pretty-print and syntax highlighting.
Software Zen: delete this;
|
|
|
|
|
How's the crash stack look like? I've been using Windows.Forms for a decade or so and no issues so far, except that one case where my app crashed on Mono which I solved reading the crash stack.
Well, I had another interesting crash, an memory overflow. I was creating an object in an event handler and using the object in another event handler. .NET dealt with that just fine, Mono not so much. Since this thing had to run on a Raspberry Pi (so no .NET), I restructured the code.
|
|
|
|
|
The only times it has ever 'crashed', i.e cannot show the design window, is when I screwed up the code. I think you need to look closer at what you are doing. But if you have solid evidence that it's a bug in the IDE you could always report the problem to Microsoft.
|
|
|
|
|
Yeah, I am with the others in that I've been using WinForms for well over a decade and the only times that the designer has gone tango-uniform is when I've monkied with the designer code myself and dorked something up. We use the Infragistics controls extensively and we've had a few times where the UltraWinGrid has lost it's styling settings but those times are pretty rare. All in all I've not had any significant issues with VS (2008, 2010 and now 2015) and WinForms. (knocking on wood...)
|
|
|
|
|
I've actually had a better time working in winforms then WPF, when I update a graphic, it shows right away in winforms designer, but the WPF cashes the original image until i restart visual studio, but the compiled version shows correct  ? more than half time the properties side bar in the designer refuses to update or allow me to click on anything in WPF, so I revert back to typing in xaml which I highly dislike.
And yes I could use Blend that seems to work well, but i dislike jumping out of the environment that I'm working in for a small tweak, like changing an image.
I can't remember winforms designer having any more crashes than the WPF designer
|
|
|
|
|
I've been using WINKEY+SHIFT+S to "clip" screenshots for a while - it's really handy for CP problem reports for example.
Now suddenly - since I installed a pen on the Surface - when I do that it opens "Snip & Sketch" (an MS Ink applet) to annotate it.
Only problem is, this is a desktop computer, and it doesn't have a pen - so why, Microsoft, are you playing around with it?
It was bad enough with the Wookietab and your deciding that since it had a US keyboard so did my desktop: I don't need you "synching" app between them ... 
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I am surprised that you are surprised 
"If we don't change direction, we'll end up where we're going"
|
|
|
|
|
Doesn't do anything (on Win7).
/ravi
|
|
|
|
|
OriginalGriff wrote: WINKEY+SHIFT+S
That's awesome! 
|
|
|
|
|
Useful!
The "Snip and Sketch" app intercepts it after you have taken it and lets you draw or type over the top before copying it back to the clipboard so you don't have to load your favourite graphics app to do a simple red circle or similar. You can install it for free: Get Snip & Sketch - Microsoft Store en-GB[^] but it's added when you enable Ink on a surface, which makes some sense.
I guess it's handy, but ... I'd rather this system didn't get apps without me knowing ...
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I got the Snip & Sketch app (comes default with Win10), which I always use.
It's easier to just use win + shift + s though
|
|
|
|
|
I think it is an awesome short cut also. I will have to remember it.
So many years of programming I have forgotten more languages than I know.
|
|
|
|
|
did you put in a ticket with Microsoft asking them this question, because I am pretty sure none of us can answer it.
|
|
|
|
|
No, I don't like wasting my time.
I put in a bug report with VS2005 and I'm still waiting for it to be fixed ... in VS2019.
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I think that the Snip & Sketch tool is new and supposed to be a replacement to the old Snipping tool...
Microsoft's Snipping Tool replacement gets new name, capture options - MSPoweruser[^]
Anything that is unrelated to elephants is irrelephant
Anonymous
-
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-
Never argue with a fool. Onlookers may not be able to tell the difference.
Mark Twain
|
|
|
|
|
Wow! Works awesomely on Win10! 
/ravi
|
|
|
|
|
Griff on Windows 7 I just use the Print Screen key and paste into Paint guess I need to try
WINKEY + SHIFT + S
|
|
|
|
|
It gives you more flexibility: instead of just "whole desktop" or "focussed Window" you can select just the bit you want - which can include foreground and background windows simultaneously.
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
