My ASP.Net site has been on a 2003 server for years and it's about time I switched to 2008. Is there a standard migration guide, or should I simply upgrade my site in VS 2010, request migration to 2008, install my new site and then when everything is working contact DiscountASP to cancel my 2003 plan? Anything else I need to know?
That's not exactly how it works, I'm afraid. Once migration begins, the site on the old server is gone. It can't be accessed on both servers. You have to do your troubleshooting and upgrading in your local dev environment. When you're relatively confident that you've covered all the bases, just open a support ticket and they can get you started on the move.
Thanks. On the technical side - is it possible to run ASP.NET 1.1 web services on the 2008/IIS7 servers?
Which causes a problem for me and leads me to the question - is there any plan to cease providing the 2003/IIS6 web hosting service for those of us that are already using it? The same question applies to SQL Server 2005 - is there an expected date when DASP will force us to migrate to SLQ 2008?
No, we haven't discussed the possibility of forcing migration from the IIS 6 servers, and I don't know that we ever will. With virtualization we can retire the old hardware but continue to support the older technologies on new servers. The problem isn't the servers, the problem is at some point Microsoft says, "Okay, no more updates for this," and at that point the technology becomes vulnerable. So I can foresee us leaving the IIS6 servers running until that time comes. I don't have their end-of-life schedule in front of me, but I would imagine that the EOL for Windows 2003 is still very far in the future.
