|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Framework and Window 2003All,
We have a production sever that has window 2003 and currently run ASP applications. I would like to run ASP.NET 2.0 along side ASP. It appears that the framework 1.1 is already installed but I'm not sure how to verify. My assumptions is that all I need to do is install the framework 2.0 but since this is a production server I would like to make sure its done the right way. If one of you experts can tell my what I need to do and why so that I can understand for future reference. Also, I saw online posting mentioning the aspnet_regiis. What does that do and is it needed? Jamal Jamal wrote:
> All, Yes, 1.1 is already installed on windows server 2003, but you'll need to > > We have a production sever that has window 2003 and currently run ASP > applications. I would like to run ASP.NET 2.0 along side ASP. It > appears that the framework 1.1 is already installed but I'm not sure > how to verify. My assumptions is that all I need to do is install the > framework 2.0 but since this is a production server I would like to > make sure its done the right way. If one of you experts can tell my > what I need to do and why so that I can understand for future > reference. > Also, I saw online posting mentioning the aspnet_regiis. What does > that do and is it needed? install 2.0. aspnet_regiis is a utility that's installed with .NET that you can use to control the associations between IIS vritual folders and the .NET framework. For Server 2003, there's also an "ASP.NET" tab in the IIS application properties dialog that does some of the same things. If you just want to run classic ASP + ASP.NET 2.0, then all you need to do is install .NET 2.0 - you don't need to deal with aspnet_regiis at all since installing the 2.0 framework will install ASP.NET 2.0 and set it as the default for all IIS virtual folders. -cd Thanks cd for the quick response.
What does this meant "installing the 2.0 framework will install ASP.NET 2.0 and set it as the default for all IIS virtual folders" I'm not sure how it would effect classic ASP website and does IIS need to be restarted after the install. Also, I have multiple websites and I plan on creating a virtual directory in one of the websites for asp.net 2.0 so that I can have asp.net 2.0 running. Is that the correct way to have both running at the same time. Just to verify, I would install "Microsoft .NET Framework Version 2.0 Redistributable Package (x86)" Jamal Show quote "Carl Daniel [VC++ MVP]" <cpdaniel_remove_this_and_nospam@mvps.org.nospam> wrote in message news:uTK40Nc$GHA.4328@TK2MSFTNGP03.phx.gbl... > Jamal wrote: >> All, >> >> We have a production sever that has window 2003 and currently run ASP >> applications. I would like to run ASP.NET 2.0 along side ASP. It >> appears that the framework 1.1 is already installed but I'm not sure >> how to verify. My assumptions is that all I need to do is install the >> framework 2.0 but since this is a production server I would like to >> make sure its done the right way. If one of you experts can tell my >> what I need to do and why so that I can understand for future >> reference. >> Also, I saw online posting mentioning the aspnet_regiis. What does >> that do and is it needed? > > Yes, 1.1 is already installed on windows server 2003, but you'll need to > install 2.0. > > aspnet_regiis is a utility that's installed with .NET that you can use to > control the associations between IIS vritual folders and the .NET > framework. For Server 2003, there's also an "ASP.NET" tab in the IIS > application properties dialog that does some of the same things. > > If you just want to run classic ASP + ASP.NET 2.0, then all you need to do > is install .NET 2.0 - you don't need to deal with aspnet_regiis at all > since installing the 2.0 framework will install ASP.NET 2.0 and set it as > the default for all IIS virtual folders. > > -cd > > Jamal wrote:
> Thanks cd for the quick response. It does not affect classic ASP at all - but were you to drop an .aspx page > > What does this meant "installing the 2.0 framework will install > ASP.NET 2.0 and set it as the > default for all IIS virtual folders" I'm not sure how it would effect > classic ASP website and does IIS need to be restarted after the > install. into one of those folders, it'd run on the .NET 2.0 framework. IIS does not need to be restarted. > You can mix classic ASP and ASP.NET in a single virtual folder, but it's not > Also, I have multiple websites and I plan on creating a virtual > directory in one of the websites for asp.net 2.0 so that I can have > asp.net 2.0 running. Is that the correct way to have both running at > the same time. really a good idea as it's essentially two separate web applications that don't share session state. Better to partition them into separate virtual folders (or web sites) as you described. > Just to verify, I would install "Microsoft .NET Framework Version 2.0 Correct.> Redistributable Package (x86)" -cd Hi Jamal,
Since you've already have IIS web sites, installing .NET 2.0 Framework will automatically install ASP.NET 2.0 to all your web sites, which also will cause the apppools restart. I don't think you have to manually restart IIS again. After installed, I recommend you create a new apppool and configure your ASP.NET 2.0 virtual directory to run in this apppool. Make sure your ASP and ASP.NET applications run in different apppools. Regarding multiple websites, I think this is fine as long as the ASP.NET app run in the apppool dedicated for ASP.NET 2.0. Sincerely, Walter Wang (waw***@online.microsoft.com, remove 'online.') Microsoft Online Community Support ================================================== Get notification to my posts through email? Please refer to http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications. If you are using Outlook Express, please make sure you clear the check box "Tools/Options/Read: Get 300 headers at a time" to see your reply promptly. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscriptions/support/default.aspx. ================================================== This posting is provided "AS IS" with no warranties, and confers no rights. |
|||||||||||||||||||||||