Some things never get fixed
-
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 ! :-\
-
I could crash the WPF designer just by looking at it.
Latest Articles:
Fun Exploring Div and Table UI LayoutAre you really that ugly? ;P :laugh: :laugh:
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.
-
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've been using this designer for many years, and when it crashes it is always because I did something silly (deleting a resource used by a control, for example). I would not blame the designer at first; most of the time the issue began between the chair and the keyboard.
while (!(success = Try()));
i've had the designer crap itself without my help before but it's rare and usually easy to fix
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.
-
I could crash the WPF designer just by looking at it.
Latest Articles:
Fun Exploring Div and Table UI LayoutMy C#/WPF app uses some
*.hfiles 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; -
Many years ago I worked with Visual Studio pre .NET using Basic and C++. Please remember that Windows forms is a code generator. Sometimes it would generate buggy code and crash your work and the graphic design. I finally got out from under legacy programs. I worked in other IDEs for several years. When I got back to VS I switched to .NET, C# and WPF in one large step. I was satisficed with this environment for several years. I just started a new job with a program that was started a year ago. To my surprise it uses C# with Windows Forms. Guess what??? The code generator still crashes the program.
So many years of programming I have forgotten more languages than I know.
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.
-
Many years ago I worked with Visual Studio pre .NET using Basic and C++. Please remember that Windows forms is a code generator. Sometimes it would generate buggy code and crash your work and the graphic design. I finally got out from under legacy programs. I worked in other IDEs for several years. When I got back to VS I switched to .NET, C# and WPF in one large step. I was satisficed with this environment for several years. I just started a new job with a program that was started a year ago. To my surprise it uses C# with Windows Forms. Guess what??? The code generator still crashes the program.
So many years of programming I have forgotten more languages than I know.
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.
-
Many years ago I worked with Visual Studio pre .NET using Basic and C++. Please remember that Windows forms is a code generator. Sometimes it would generate buggy code and crash your work and the graphic design. I finally got out from under legacy programs. I worked in other IDEs for several years. When I got back to VS I switched to .NET, C# and WPF in one large step. I was satisficed with this environment for several years. I just started a new job with a program that was started a year ago. To my surprise it uses C# with Windows Forms. Guess what??? The code generator still crashes the program.
So many years of programming I have forgotten more languages than I know.
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...)
-
Many years ago I worked with Visual Studio pre .NET using Basic and C++. Please remember that Windows forms is a code generator. Sometimes it would generate buggy code and crash your work and the graphic design. I finally got out from under legacy programs. I worked in other IDEs for several years. When I got back to VS I switched to .NET, C# and WPF in one large step. I was satisficed with this environment for several years. I just started a new job with a program that was started a year ago. To my surprise it uses C# with Windows Forms. Guess what??? The code generator still crashes the program.
So many years of programming I have forgotten more languages than I know.
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 :wtf: ? 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 had the designer crap itself without my help before but it's rare and usually easy to fix
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.
-
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.