Have Geek Brain

Asp.Net 3.5 virtual directory under asp.net 2.0 site

I currently have an ASP.net 2.0 site with multiple ASP.Net 1.1 sites running virtual directories in the main 2.0 site. While this creates some problems with inheriting web.config entries from site 2.0 to sites 1.1, we were able to configure all sites to work. However, we are now preparing to migrate 1.1 sites to 3.5. Unfortunately, due to bureaucracy out of control, we are unable to update the 2.0 main site. I wanted to make sure that there would be no problem simply upgrading child virtual directories to 3.5.

My initial guess is that this will be fine since 3.5 uses the same runtime as 2.0, however I am wondering if there are any significant differences in web.config elements in 3.5 that might conflict with 2.0 elements.

Does anyone have discernment?

0


a source to share


4 answers


we did it, and as noted, it is mostly inheritance in web.config (especially if you are using the AJAXControl toolbox as 3.5 and 2.0 are different versions). Once you resolve, the sites should be fine.



+1


a source


I don't think there are any significant differences that could cause you problems, as ASP.NET 3.5 websites are only ever called 2.0 sites and it will be a 2.0 runtime reading web.config.



0


a source


It should also be noted that you cannot mix .NET versions in IIS application pools. Thus, you cannot use the same application pool for .NET 1.1 and .NET 2.0+ web applications.

0


a source


If at all possible, you should set up the same situation on the staging server, test the migration, document each step, and take troubleshooting steps, if any, to get everything working. Then you don't have to guess. :)

0


a source






More articles:


All Articles