Client Tracking Software

Can installing ASP.NET 2.0 screw up existing software on a server?

I am going in to upload a website to a Windows server that may not have ASP.NET 2.0 on it. The server currently holds a website and a proprietary software package that handles client management for a debt-collection firm. If I have to install ASP.NET 2.0 to get the new website working, could it interfere with existing software? Does the server keep the old framework as well, or is ASP.NET 2.0 backward compatible with the previous? If I didn't phrase everything correctly, bear with me. I am pretty new at the server stuff and was thrust into this by my boss - just trying to get this project done and minimize collateral damage :)

Public Comments

1. Not good to load direct to Server. Nasty bad, terrible things happen.
2. a
3. OK, this is coming from EXPERIENCE. You CAN run both frameworks now but asp.net 2.0 stuff will not run on asp.net 1.1 and vice versa. Here are some tips to make them both run in harmony. 1. If you have both of the .net frameworks installed on the computer you now have an extra ASP.NET tab on the IIS virtual directory properties section that will now allow you to select which asp.net will handle the web content. Careful because it defaults to 1.1 and you drop a 2.0 site in the directory and it complains "Framework 1.1.4.2 doesn't like this" (of course this is not the actual message but you get my point). So you will have to switch the ASP.NET in the virtual directory to 2.0. 2. If you are running Windows server 2000 or 2003, the frameworks CAN NOT run on the same application pool. Create one for 1.1 an one for 2.0 and then in the properties for the virtual directory MAKE SURE you have the appropriate application pool selected. That is it TEST THIS OUT ON A TEST SERVER ENVIRONMENT IDENTICAL TO THE PRODUCTION ENVIRONMENT FIRST. Because you will break it a few times but you will get the hang of it. It is not really rocket science. Its not really computer science. Its Microsoft. LOL Hope that helps RJ