Visual Studio 2005 Shipped With Bugs, Backward Compatibility Problems

It is only a week, since Visual Studio 2005 RTM was shipped and already one can notice some frustration among bloggers with the quality of the IDE. Check it out:

• Wesner talks about beta2 - RTM conversion.
• ISerializable talks about troubles converting a "small Winforms project".
• Frans Bouma testing Generics (IDE hangs). See some crash experiences in the comments to his post.

Today's morning I tried to convert a small Web Solution (6 projects) to Visual Stusio 2005 (I've already had some experience converting Web Projects from Visual Studio 2003 to Visual Studio 2005 Beta 2). I don't want to speak about warnings and a lot of uninformative build error messages (like for example that Global is ambigous name for a class and alike). I managed to compile (making several IDE restarts). But I'm still not able to run the application since web.config is broken :( I'm also frustrated with the fact that the new Web Site model can not handle page paths effectively, can not recognize a Web Site configured in IIS, etc ...

Related Posts:

• SQL Server 2005 and Visual Studio 2005 - RTM
• Visual Studio: How to Debug Script Code
• VS 2005 beta 2 -- Exclude From Project Issue
• Asp.Net 2.0 and VS 2005 Beta 2 Bugs
• Visual Studio 2005 Beta Experience Program
• Visual Studio 2005 Beta 1 with Team System Included
• Installing VS 2005 Beta 1
• Visual Studio 2005 Beta 1
• Bug in May 2004 VS 2005 CTP ?
• Visual Studio May 2004 Community Preview Experience (Part 2)

Hi Anatoly,

The symptoms you are describing (not handle page paths effectively, can not recognize a web site from IIS) sound like you are using a web project as a file-system web project (a new feature in VS 2005) and not as an IIS project.

This post talks about how to use IIS webs in VS 2005: http://weblogs.asp.net/scottgu/archive/2005/08/23/423409.aspx

This should fix the problems you are having.

Hope this helps,

Scott

So I come in this morning and start catching up on the 339 unread
rss feed posts in my reader. ...

GUI is buggy too. Very simple things like this: Change a ToolStripStatusLabel1's Spring to True using Properties. In the Form, right click the ToolStripStatusLabel1 and Spring is not checked.
Changing True/False for ToolStripStatusLabel1's Spring property will not update the Spring CheckedState in the right click menu of ToolStripStatusLabel1

A very small VB.NET Solution with 4 Projects takes like 5 minutes to Rebuild.

McoreD: rebuilding seems to work ok as far as I can see

Scott: I see some differences from the article, but your post really helped me, thanks

Another sleepless night, so I’ve been catching up on the hundreds of unread RSS items in my feed...

Hummm ....
Today I read some news about VS.NET 2005 RTM. Some good ... some bad. I like good first....

I am so TIRED of micrsoft buggy IDE. I have been using it from the first beta (november 2004 I think) and I am SERIOUSLY anoyed. Everything from the IDE getting the latest version from VSS and the IDE crashes and looses all my changes to the IDE regularly throwing errors int eh Winform designer. Productivity has actually gone DOWN in y dev team since we started using the RTM.

Dare I say next project I will use VS.NET 2003 or even JAVA and Eclipse.

Hi

I am having an issue with VS 2005. It run ok from IE and I have IE 7, but when I run it through the interpreter, it fails to find
service.useService and fails.

I have had a few other problems with relative paths too.

Could you help.

VK

VK: You are talking about debug, right ?
Do you have problems with IE 6 ?