• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 821
  • Last Modified:

How do I run .Net 1.1 and .Net 2.0 side-by-side

On our production site we have an ASP.Net 1.1 website
In preparation to roll out a new version (that uses 2.0) we installed .Net 2.0 on that machine. Immediately .Net 1.1 site stopped working with error:

Unrecognized attribute 'requirePermission' (C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Config\machine.config line 14)

I've seen a lot of ideas on the net but none that seem to fit. This website is at the top level so it's not contained in any other virtual folder.

If I go into the IIS admin and set it to run as ASP.NET version 2.0 then set it back to 1.1 and hit OK, that fixes it - but it's always broken again the next morning and I have to do it again. I suspect that's due to the application pool rebooting the .Net worker process.

One odd thing I see is if I view the properties of the top-level "Web Sites" folder in IISAdmin it says it's running ASP.NET 1.1 but it points to a config file in the 2.0 directory. See attached

I'm guessing if I fix this inconsistency I might fix the problem but am unsure how to proceed.
iisadmin.JPG
0
jerelmcdonald
Asked:
jerelmcdonald
  • 2
1 Solution
 
indianguru2Commented:
Run .Net 1.1 and .Net 2.0 in different Application Pools.
0
 
jerelmcdonaldAuthor Commented:
Thanks for the response. The .Net 1.1 site is in its own application pool. In fact there are no .net 2.0 sites on the machine, we just installed .Net 2.0 but haven't deployed any 2.0 website yet.

I think it needs aspnet_regiis run to clear up the conflict shown in the screen shot above (the properties screen of the "Web Sites" folder that contains all web sites. I'll try this tonight during off hours and report back although I'm not sure if that will make it worse or better.

I don't understand why I can set it to 2.0, then set it back to 1.1 and that fixes the problem -- until the next morning which I think coincides with the web application pool restart.
0
 
jerelmcdonaldAuthor Commented:
This fixed it:

C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis i
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis -s W3SVC/1890615468/root/

Now I'll probably need to do some more work when I add the 2.0 sites - probably make the root 2.0 and go from there.
0

Featured Post

Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now