|
Home > Archive > IIS Server > July 2005 > Migrating to Win Server 2003
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Migrating to Win Server 2003
|
|
| Grady Nash 2005-07-29, 6:00 pm |
| My production ASP.NET site is running on Win 2000 and IIS 5. I'd like to
migrate this to Win 2003 and IIS 6. I also have 2 QA web servers, and Build
server and each developer has a web server all running Win 2000 and IIS5.
My question is can I keep my developers and Build box running Win 2000, and
upgrade one of my QA boxes to Win2003? Will the DLL I built in Win2000 run
properly on Win2003 and IIS6. My site is using .NET framework 1.1 SP1.
If I upgrade my Build box and my developers to Win 2003, will the DLL run OK
on Win 2003?
Any good links on problems with migrating to Win 2003 and IIS6.
Thanks,
Grady
| |
| David Wang [Msft] 2005-07-30, 2:48 am |
| I presume you are referring to the .Net Assembly DLLs?
If so, then synchronizing ASP.Net versions on IIS5/IIS6 is more important
than anything else.
The largest "difference" I can think of between ASP.Net on IIS5 and IIS6 is
due to the IIS6 Process Model. If you run IIS6 in IIS5 Compatibility Mode,
ASP.Net should behave like IIS5. If you run IIS6 in default Worker Process
Isolation Mode, then most ASP.Net "process model" settings are ignored so
you get the IIS6 defaults -- but you can reconfigure IIS6 Application Pool
to behave like ASP.Net's. This includes process identity, process recycling
period, memory recycling metric, etc.
Otherwise, I'm really expecting it to just work... unless you have other
sorts of dependencies like database access, user accounts, ACLs, etc.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Grady Nash" <GradyNash@discussions.microsoft.com> wrote in message
news:00F129A2-CCDB-430D-AE75-1E162030B6DA@microsoft.com...
My production ASP.NET site is running on Win 2000 and IIS 5. I'd like to
migrate this to Win 2003 and IIS 6. I also have 2 QA web servers, and Build
server and each developer has a web server all running Win 2000 and IIS5.
My question is can I keep my developers and Build box running Win 2000, and
upgrade one of my QA boxes to Win2003? Will the DLL I built in Win2000 run
properly on Win2003 and IIS6. My site is using .NET framework 1.1 SP1.
If I upgrade my Build box and my developers to Win 2003, will the DLL run OK
on Win 2003?
Any good links on problems with migrating to Win 2003 and IIS6.
Thanks,
Grady
|
|
|
|
|