VS 2005 HELL!!!

DISCLAIMER: Rant on Visual Studio 2005 (especially VB.Net)

I have to say I am really REALLY disappointed by Visual Studio 2005, especially the VB.Net side of things.

After a long struggle with management to move towards 2.0 and VS 2005, and citing 2005's new and improved features I finally managed to get our dev team on 2005.

Now, things run smoothly with our C# projects, but VB.Net is another issue. The IDE shuts down at least 5 - 10 times in a day and this is not just for one person but the entire dev team. I even had most of our machines upgraded thinking it might be a memory issue but that didn’t help either. The IDE just stops with that stupid Error Reporting dialog for no particular reason. Sometimes it’s while popping intelisense, opening up xml files (not large files at all), and sometimes even while building.

After almost 6 months of delay from the Microsoft one would expect that this version would at least be at par with 2003 and bugs would be kept at a minimum. While working on our C# projects we don’t see the same behavior but when working with VB.Net its worse than Eclipse!! (and i think Eclipse is one of the worse IDE's I’ve ever had the displeasure of working with).

Please VB.Net IDE team if you read this post, PLEASE PLEASE PLEASE fix these bugs. Not only are they annoying but its things like these that make us regret the decision of migrating to VS 2005. (God knows how I'm going to explain these issues to management...)

Has anyone else experienced these issues??

- Ritesh

Could this be the same issue you're experiencing?

andokai wrote:

Could this be the same issue you're experiencing?

It seems to be the same issue. I'll try to get down the Hot Fix and apply on a couple of machines and see if that fixes it.

Thanks andokai, you've been of great help!!!

- R

blatzcoder wrote:

Microsoft^®.  Always in beta.

No, that's Google

blatzcoder wrote:

You're right. I should have elaborated a bit better. In Microsoft lingo:

Shipped product = beta

Nope, that's still Google. GMail, Groups, Froogle, etc... Is anything of theirs not a beta?

I've largely moved from VS 2003 to 2005 for Compact Framework 1.0 development. I'm finding it a lot quicker and more stable, especially when debugging. That's my experience, though.

At home, C++ Smart Device projects are broken - it simply says 'create failed' on the status bar. This may be due to IE7 Beta 2 Preview though (not installed the latest version yet) since the project wizard is an HTML dialog.

C# isn't immune. In fact the code editor is virtually useless with any good sized class file, which happens all of the time with Winforms stuff.

Yes, this is betaware and brutally slow and flaky.  MS should be ashamed that they released this thing.  They gotta stop listening to their paying customers like Boeing and start listening a lot more carefully to everyone else.

If this is how Vista is being developed, it's going to be a disaster.

I tell you the truth.

I expected VS2005 To be Rock solid for developers.

But alas, I was disappointed. Its IDE just sucks big time. It not stable and its slow as hell, and my machine is fast..

I mean what is microsoft playing at

Yes, its slows down my machine (Dell Latitude C640 P42.4 & 1GB RAM). Especially when I open my Windows Forms project where it needs to load all the datasets inside my project.

Does anyone knows why VS2005 must load all those datasets when I open my project?

Very little software is 100% bug free when shipped. Sometimes the bugs are not yet discovered where as sometimes the deadline is too near and the bugs found are very damaging.

Anyway, as you all would have known. To wait for a software to be 99.99% bug free, that software won't be shipped forever.

As for new version of a software, have anyone seen a newer version of a software that is faster than its predessesor?

Windows XP is faster than Windows 2000 Professional... Right?

hosy wrote:

Windows XP is faster than Windows 2000 Professional... Right?

It is, actually, on quite a few computers I've used it on.

Back to the original point, though - the problem isn't with VS2005 being buggy - all software is buggy. The problem is that its level of bugginess is appropriate for a v1.0 product, not a v2.0 product. We had the same sort of things with VS2002, until VS2003 came and fixed most of the problems.
I'm guessing that the changes made in VS2005 were so widespread and fundemental, it can almost be considered a v1.0 release of a whole new product with all the expected instability.
The problem isn't with the product itself - it's still an excellent product, IMO - but with people's expectations for it as a 2.0 release.

We are a VS2003 ASP.NET/VB.NET shop.  My boss is of the mindset to upgrade to VS2005, even though we really don't need it.  I will be thouroughly testing our projects in VS2005 after reading posts like this.  We built our company on .NET when it was in Beta 1/2.  So far, the experience has been great.  Very few complications.  5 years later, and upgrade to VS2005 has many consequences if the transition is not painless.

Red5, I would tell your boss to wait at least until there is a service pack out.

I'm sorry, but I have to say VS 2005 is easily *the* worst Microsoft developer product I have *ever* used in my 10+ professional years.

The worst part of IDE are the constant crashes if using visual inheritance.... LoaderException every 30 secs or so... and the only workaround is either to clean the solution or to restart the IDE.

I can put up with *some* number of bugs, but this is just too much crap in one single product, with no service pack in sight in reasonable time.

Also, the problems seem so easily reproducable I really have to wonder if Microsoft has any QA at all, or maybe they are all busy writing blogs, and rescheduling Vista.

There. I vented myself. I feel better. Now let's restart that IDE once again.

What features of VS2005 are you guys using that are causing so much problems?

James

zhuo wrote:

What features of VS2005 are you guys using that are causing so much problems?

James

The ide and the compilers.