Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post May 21, 2012 11:25 AM by LittleJohn
May 10, 2011 05:43 AM|LINK
i have windows server 2003 r2 standard edition in my production server.
in that server we have used visual studio 2005. then applictaion under the 2.0 working fine.
now we installed visual studio2010 framework.
we have iis6.0 version in our production server.
in iis i was created sample website and going to change the asp.net version. so during that i have received the warning message like this
"changing the framework requires a restart of w3svc service.alternatively you can change the framework version without restarting the w3svc service running:aspnet_regiis.exe -norestart -s iis-virtual path . do you want to continue"
this message shows during asp.net version changing.
so my query is if i changed that into 4.0 then remaining appllication are running in 2.0 version(all are in live).
so it will affect the existing application when i changed my test application version in to 4.0.
i need the suggestions regarding this.
May 10, 2011 09:45 AM|LINK
The changes will affect only your new ASP.NET 4.0 application, but you should also create a new application pool for it.
May 12, 2012 03:58 AM|LINK
When you change the ASP.NET version for one app, it will change it only for that app. However, since you need to restart the IIS, it will restart all of your websites, which is a bit annoying. Microsoft has provided some indirect way to
change the .NET version without restarting IIS, but I wonder why Microsoft did not make it easy for everyone by integrating the option with IIS
Here is the command to use to change .NET Framework version on IIS without restarting it:
aspnet_regiis -s w3svc/881126637/root -norestart
In the above example, 881126637 is the App Id. You should replace it with correct App Id of your app pool.
Read the detailed steps here:
May 21, 2012 11:22 AM|LINK
Change the framework version will not cause any problem to your existing website as it is upper version of .net framework.
May 21, 2012 11:25 AM|LINK
Upgrading .NET version can cause a lot of issues for ASP.NET websites since all new versions come with several changes that could break existing code. Most of them are related to added security features in new versions.