10 ms·
Whose brilliant idea was it to MAKE THE MENUS SHOUT AT YOU? Glad to see there's a registry key to fix that... but still, when did Microsoft start listening to
by NateDad 14y ago
Whose brilliant idea was it to MAKE THE MENUS SHOUT AT YOU? Glad to see there's a registry key to fix that... but still, when did Microsoft start listening to my great aunt Gertrude about proper capitalization?
Also, I agree, the reviews aren't hitting the most important points about the new VS. Does it fix all those annoying bugs we've all been struggling with for 10 years? My guess is no (since as I said, most of them have been there for over a decade). Instead of putting time mucking with the look and feel on a tool that is SOLELY used by developers... how about fixing the bugs that cause us to lose hours of time every week? You know, like where VS crashes, or decides it can't load dependencies in installer files, or the horribly slow search, or the occasional complete hang of the UI for 20 seconds, or the fact that a minor change to an installer project completely changes the whole incomprehensible project file? How about those bugs?
But I guess most of this product was just supporting the new metro crap. Shouldn't OS compatibility be the Windows SDK team's problem, and let the Visual Studio guys... like, you know, work on Visual Studio?
- beanbeans 14y agohey NateDad 2 things when VS is choking on some simply whatever launch tasks manager , look at disk performance youll see its writing files in user\appdata\roaming somthing like that erase all MS files in that dir. also create your own build automation and dont count on anything but compling from VS .MSFT is returning to its roots as a tech marketing but vs2010 should work OK for another 2-3 years, by then you can migrate to somthing better.good luck!!