.net version for entire website erroneously being changed
.net version for entire website erroneously being changed:
We are using ISLE 2011 to install an ASP.NET app to IIS on w2003 and 2008. We want the setup to create the new app in the existing website (if any), and set the .net version of this new app to .net4 - but do NOT change the .net version of the root site or any other apps in the site. To try to do this, in isle iis view we create a new website with port=80, sitenumber=0 (that is, use the existing site, if any), and left the site's "ASP.NET version" property blank. We then created our new app in this site, and set the ASP.NET version to 4.0.30319.
This does not work. After the installer runs, the existing web site, and all existing web apps, are moved to a new .net 4 app pool called "ASP.NET v4.0 Default App Pool". We looked in the win installer log, and it seems ISLE is executing aspnet_regiis.exe 3 times: 1) aspnet_regiis.exe -ir (this installs aspnet.) 2) aspnet_regiis.exe -k w3svc/1/root 3) aspnet_regiis.exe -s w3svc/1/root
I think #2 and #3 are the problem - shouldn't they be for just the new app, not the entire root (that is the website)? This install breaks .net 2 apps that currently exist on the server.
How can we get ISLE to use the correct path for #2 and #3?
Update: the problems reported in the previous post happens when installing on win2008.
When installing on win2003, we also have problems, but the installer behaves differently: -no new app pools are created. So, all existing apps and the new app end up attached to the one and only app pool -the existing apps are correctly left at their original .net version (2), and the new app is correctly set to .net version 4. -this config, of course, does not work either, because a single IIS6 app pool cannot support more than one version of .net. So, the first app started after the pool is reset defines the .net version of the pool, and no other apps will run. For example, if the old (net v2) app is started, it works, but then starting the new app fails. restarting the pool, and then reversing the app start order, results in the new app working and the old app failing.
Looking at the msi log for 2003, it is different than on 2008: 1) aspnet_regiis.exe -ir (this installs aspnet.) 2) aspnet_regiis.exe -k w3svc/1/root/[newapp] 3) aspnet_regiis.exe -s w3svc/1/root/[newapp]
So, the behavior is diffence is explained, but the reason why ISLE does different commands based on 2003 v 2008 in regard to this is still a question.
So, right now it appears ISLE doesn't support installing a new web app onto a server that has existing .net web apps that use a different .net version - it fails (in different ways) on both win2003 and win2008.
On IIS6.0 you can create application pools and assign different web applications to different pools. And you can configure each pool differently.As you know, that within one application all applications have to use same version of .Net framework .
Hence if you have applications that need to use different versions of ASP.Net, then create separate pools. Put all .Net 2.0 web applications in one pool and all .Net 4.0 applications in another pool.
