It’s been one of those weeks ![]()

It should be noted that I was able to take a screen shot, upload it to WordPress and make this blog post before that message went away and I was able to interact with Visual Studio.NET again!
It’s been one of those weeks ![]()

It should be noted that I was able to take a screen shot, upload it to WordPress and make this blog post before that message went away and I was able to interact with Visual Studio.NET again!
You are spot on ! it *IS* a piece of shit. They have so many bugs that crash Visual Studio if you are using MFC. It seems that once you start compiling and debugging, you are then FROZEN from adding any further new classes via their piece of shit class wizard.
Another thing that I can’t stand is the HTML dialog boxes. Why can’t they give you an option to use CDialog instead.
I had to go back to the one that *REALLY* works, VS 6.0 MFC.
I had the same thing happen with a few days left to launch on a huge project.
HULK WANT SMASH!
Agreed. VS2008 is a buggy piece of shit, especially on Vista64. I’m going back VS2005.
It has worked much better since I switched over to Windows 7. Even with 64-bit Windows 7 it runs much better.
My problem before may have been more Vista than VS.NET 2008.
full agreement. Don’t use this SHIT
It’s the worst piece of shit I’ve ever had the displeasure of working with. It just plain sucks!
Indeed – both it and 2010 are utter shit, written by morons. 2010 won’t even install, let alone work.
Came here to agree. VS2010 is such trash it’s unbelievable. How does a company with so many resources ship such intensely buggy software? Jeez…
Indeed – it’s a piece of – frustrating – crap! It just keeps freezing and crashing. (trying to refactor a large solution, so lots of interaction with solution explorer….)
Why it’s just expanding the setup project most of the time, is beyond me. The support for these kind of projects is not even complete (MSbuild does not support it).