So I'm in charge to deploy my project on the productive server where some other ASP.NET-Websites are also set up.
The problem now is that I wrote my whole project under .NET 3.5 but on the webserver the current installation is .NET 1.1 as some of the other projects require them (don't ask me why, I can't figure it out either but my PM says so...) and thus I'm not allowed installing 3.5 for now but I'm not at all in the mood of rewriting my project on 1.1.
Now; is it possible (and if yes, how) to manage multiple installations of .NET, so sort of assigning the projects which version to use? (Say: Project X use .NET 1.1, Project Y use 3.5) or are there possible conflicts that could crash one or another of the projects when I install 3.5?
Different .NET framework versions can be assigned per virtual directory in IIS (provided that these two virtual directories are assigned to different application pools). So if you have two virtual directories in your web server say App1 and App2 you can assign App1 to use .NET 1.1 and App2 to use .NET 3.5 or more precisely ASP.NET 2.0. For this to work you need to install .NET 3.5 on the server.
Yes, it works, see the screenshot by Darin. Note, though, that .net 1.1 and .net 2 CLR (= 2.0, 3.0, 3.5) applications need to run in different application pools (you will receive an error when accessing a .net X web application which runs in the same pool as an already running .net Y web application).
PS: I've found a tutorial on setting up different app pools for side-by-side running of asp.net 1.1 and 2.0.
Yes this is possible.
You can have Apps running .Net 1.1, Apps Running .Net 2 CLR (2.0, 3.0, 3.5) and also Apps running .Net 4.0
