Visual Studio Survey!
-
How many people actually continue working when Visual Studio says, "You can continue working while the designer is loading in the background?" I know I don't. I'm in the zone, coding marvelous features, and then suddenly it comes to a screeching halt. I can't continue working because the designer is not loaded yet. Geez. :rolleyes:
The difficult we do right away... ...the impossible takes slightly longer.
Well, so far i just accepted that in 90% of cases the designer will die. So i code a bit more, wait for the confirmation it died and the restart visual studio or rebuild in hope to fix the designer.
MessageBox.Show(!string.IsNullOrWhiteSpace(_signature)
? $"This is my signature:{Environment.NewLine}{_signature}": "404-Signature not found"); -
How many people actually continue working when Visual Studio says, "You can continue working while the designer is loading in the background?" I know I don't. I'm in the zone, coding marvelous features, and then suddenly it comes to a screeching halt. I can't continue working because the designer is not loaded yet. Geez. :rolleyes:
The difficult we do right away... ...the impossible takes slightly longer.
-
How many people actually continue working when Visual Studio says, "You can continue working while the designer is loading in the background?" I know I don't. I'm in the zone, coding marvelous features, and then suddenly it comes to a screeching halt. I can't continue working because the designer is not loaded yet. Geez. :rolleyes:
The difficult we do right away... ...the impossible takes slightly longer.
Richard Andrew x64 wrote:
"You can continue working while the designer is loading in the background?"
Knowing MS, I always read that as "you *can*, but probably *shouldn't*". Pet peeve: When VS crashes, and the next time you restart, it prompts you whether you want to reload a given set of files from Folder A, or its backup from Folder B. And you have no idea how they differ. If there's a screen that needs a Diffs view, it's that one.
-
How many people actually continue working when Visual Studio says, "You can continue working while the designer is loading in the background?" I know I don't. I'm in the zone, coding marvelous features, and then suddenly it comes to a screeching halt. I can't continue working because the designer is not loaded yet. Geez. :rolleyes:
The difficult we do right away... ...the impossible takes slightly longer.
I've never used the WPF Designer, and I've been developing for WPF since Visual Studio 2008. They're slow, buggy, and add arbitrary
MarginandPaddingvalues to everything. In my experience, the only way to get a nicely flowing UI is to use hand-crafted XAML.Software Zen:
delete this; -
How many people actually continue working when Visual Studio says, "You can continue working while the designer is loading in the background?" I know I don't. I'm in the zone, coding marvelous features, and then suddenly it comes to a screeching halt. I can't continue working because the designer is not loaded yet. Geez. :rolleyes:
The difficult we do right away... ...the impossible takes slightly longer.
I always wait. I think it started to show up when they introduced out-of-process designer in VS for WinForms.
-
How many people actually continue working when Visual Studio says, "You can continue working while the designer is loading in the background?" I know I don't. I'm in the zone, coding marvelous features, and then suddenly it comes to a screeching halt. I can't continue working because the designer is not loaded yet. Geez. :rolleyes:
The difficult we do right away... ...the impossible takes slightly longer.
Which designer? Windows Forms or XAML? I have not had a problem continuing my work on the rare occasions I get a message like that in WinForms. I don't use the XAML designer, since it does support Xamarin, MAUI, WinUI, etc.
-
I've never used the WPF Designer, and I've been developing for WPF since Visual Studio 2008. They're slow, buggy, and add arbitrary
MarginandPaddingvalues to everything. In my experience, the only way to get a nicely flowing UI is to use hand-crafted XAML.Software Zen:
delete this;I second this. Compare a before and after of the XAML if you use the designer to change anything. The change usually generates a crap-ton of XAML - or did several years ago, the last time I tried to use it. I do everything in XAML manually within the actual XAML.
Mike
-
How many people actually continue working when Visual Studio says, "You can continue working while the designer is loading in the background?" I know I don't. I'm in the zone, coding marvelous features, and then suddenly it comes to a screeching halt. I can't continue working because the designer is not loaded yet. Geez. :rolleyes:
The difficult we do right away... ...the impossible takes slightly longer.
vs2022 is irritating the heck out of me. Why is VSCode so liked - simplicity. VS2022 has so many dang options, features, etc it's ridiculous. The default installation should have 10% of what they are showing. Under file: 19 options Edit: 23 View: 33 etc. Even help is out of control. I watched a few tutorials on Resharper and said no way...
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
-
OK :laugh: Yes I think VS 2015 was before they instituted the out of process designer.
The difficult we do right away... ...the impossible takes slightly longer.
This article has few words about the out-of-process designer and compatibility: [WinForms in a 64-Bit world - our strategy going forward - .NET Blog](https://devblogs.microsoft.com/dotnet/winforms-designer-64-bit-path-forward/)
-
This article has few words about the out-of-process designer and compatibility: [WinForms in a 64-Bit world - our strategy going forward - .NET Blog](https://devblogs.microsoft.com/dotnet/winforms-designer-64-bit-path-forward/)
Thanks for the article. I did happen to read that article when trying to research a problem that I'm having with the out-of-process designer!
The difficult we do right away... ...the impossible takes slightly longer.
