I have a Windows 2000 IIS5 server with around 40 apps on it. These apps vary in size and complexity but it represents about 9 years of dedicated application development time so the amount of code deployed is NOT insignificant. We have always been very please with the functionality and stabiltiy of this server but we are finally starting to hit the wall on some new development we are doing (for instance, support for Office 12 drivers).
We are also pretty familiar with Windows Server 2003 IIS 6. However, if I'm going to dedicate team time to deploying, testing, and refactoring for IIS6, I am tempted to move to IIS7, go through the upgrade cycle just once, and be able to stay put for a while again.
So, I'm looking for advice from app dev'ers. Is there an upgrade path from Windows 2000 IIS5 to Windows 2008 IIS7? Is it worth transitioning to IIS7 or go for the much easier transition to Win2K3/IIS6? Do I need to go from Win2k-->to Win2K3-->to Win2K8 for a successful upgrade?
ANY advice is appreciated.
Thanks
Ryan Hunt
We are also pretty familiar with Windows Server 2003 IIS 6. However, if I'm going to dedicate team time to deploying, testing, and refactoring for IIS6, I am tempted to move to IIS7, go through the upgrade cycle just once, and be able to stay put for a while again.
So, I'm looking for advice from app dev'ers. Is there an upgrade path from Windows 2000 IIS5 to Windows 2008 IIS7? Is it worth transitioning to IIS7 or go for the much easier transition to Win2K3/IIS6? Do I need to go from Win2k-->to Win2K3-->to Win2K8 for a successful upgrade?
ANY advice is appreciated.
Thanks
Ryan Hunt