Everyone seems to be quiet on this. We have already SP1 out for both VS2003 and VS2005 but seems like that many issues are yet to be fixed...
Suppose the following scenario:
- Create ASP.NET application in VS2003.
- Compile it, test.
- Create a MSI setup in VS2003 (I'm still in the same solution).
- So, take your MSI and deploy it to another computer.
The bug: When MSI is installed on that another computer - it is installed under IIS virtual derectory and the application is configured as .NET 2.0 runtime application in IIS by default. You cannot know this until you browse IIS administration panel for that application.
Which can cause unpredictable results, since:
- This scenario is not tested.
- It forces rendering as XHTML compliant, while VS2003's ASP.NET generated HTML is not XHTML compliant. Like it renders ClientID as ctl00_controlId if we use master page, while ASP.NET 1.1 renders it the other way.
- Not to mention .NET 1.1 does not support XHMLconformance tag in web.config.
- The application is not performant since it was not compiled under the runtime it runs.
- There are other incompatibilities since ASP.NET 2.0 is not fully backward compatible with ASP.NET 1.1.
If you ask - there is a reason why the application is build with VS2003 and not VS2005.
My advice: instead of being so enthusiastic about reporting bugs fixed in VS2005 SP 1 or reporting getting MVP awards (for answering the same questions in forums year after year ?) - start to take care of real things.
P.S. And for god sake - why is it impossible in VS2005 to compile for .NET 1.1 runtime ?
Friday, January 5, 2007 3:06 AM