Last post Jul 11, 2007 06:12 AM by naturehermit
Jul 10, 2007 04:58 PM|quantass0|LINK
We're considering upgrading to MS
Visual Studio 2005 from VS 2003. Our concern is backwards compatability with existing web apps. At the moment we have several applications running under ASP.NET v1.1 (mostly in C#) on our Win2K3 box. We intend on using the capabilities of .NET v1.1 for
at least another year or so as we have several existing apps that were composed under VS 2003 and .NET v1.1.
My quesitons are:
1. Our IIS Web Site is set for ASP.NET 1.1 framework. Is VS 2005 capable compiling code that is still compatabile with our existing
ASP.NET v1.1 portal (we use Rainbow Portal) and the existing .DLLs / Source in production that were compiled using VS 2003 / .NET v1.1 ? Can all this code intermingle and run fine under our current web site?
2. Is VS 2005 capable of outputting both .NET v1.1 and 2.0 assemblies?
3. I've heard of VS 2005 converting 2003 projects to 2005 projects. Is the change so radical that our existing .NET 1.1 website will not be able to function with it (ie. is web.config, ascx, and aspx with code-behind still the backend structure) ?
Jul 11, 2007 05:05 AM|venton|LINK
I have just upgraded a fairly complicated web site from 2003 to 2005. It consisted of web pages, and class modules and some non asp.net code.
Although I had VS2003 professional, I purchased VS2005 standard upgrade and it did everything I wanted.
No VS2005 cannot output 1.1 dlls.
You need to open your old project / solution in VS2005 and it will upgrade it via a wizard. After conversion you then right click each project and say 'convert to web application'.
By doing this, you get the same model as 1.1 eg single dll's and .aspx ascx files etc.
I found that none of my .aspx ascx etc files were touched by the upgrade which was great. All I had to do was overwrite the 1.1 dlls with the 2.0 dlls on the live server, which is great for a live application and can all be done in a few seconds.
The only issue I had was that you may need to create a new application pool for NET 2 and set your app to run under that pool, and tell it to use the .net 2 framework on the IIS asp.net tab.
I have found no compatibility issues at all and am pretty surprised how easy it all was. I think the key thing is to make sure you have everything backed up (eg the old dlls) so you can easily roll it back on live.
The webconfig has a couple of minor changes made to it so put that live also.
Jul 11, 2007 06:12 AM|naturehermit|LINK
The best way to handle this is to keep running your existing apps in 1.1 and should you need to modify them..do a gradual upgrade.
However any new functionality that you are developing use asp.net 2.0 and use IIS configuration to set them for .net 2.0. Both of them can sit comfortably with each other.
1. As i said above they can run quite happily with each other but VS2005 wont compile compatibile code with 1.1, the solution is to use above.
2. The VS2005 that I use (team edition) only outputs 2.0, i dont know about others.
3. Yes the change is radical. The web.config and ascx and apsx are still the same but there is lot of functionality added. Its the framework--it will simply allow/disallow things based on its setting so as i said use new functionality with 2.0 and set the
new directory to use 2.0 from IIS.