Last post Mar 15, 2009 05:31 PM by djchapin
Mar 14, 2009 11:11 AM|djchapin|LINK
I am managing a Windows 2003 server in ASP.Net 2.0 with VWD 2005 and I would like to upgrade to the ASP.NET3.5 and VWD2008 however when I updated last time it took me a week to get everything back up and running fully.
I'm right now in the middle of an add campaign, I'm a small business owner and I am a one-person shop so I have alot to manage besides the 4 websites and the server. Can you give someone like me a timeline for the transition and what the major problems
are for doing this type of transition so that I can guesstimate if it would affect the server I am working on.
I had considered that the simplest way to do this would be to rent a new server with everything upgraded and do the whole thing and then move the websites over.
ANY advice would be welcome.
Mar 14, 2009 12:04 PM|rtpHarry|LINK
Not sure what problems you had last time but installing .net 3.5 on a server should be quick and pain free.
It runs as a layer on top of the .net 2.0 libraries so you have the choice of targeting 2.0 or 3.5 in your projects. Your existing websites should continue to run without a hitch after you have installed 3.5.
Unless you have a specific need to use features from the 3.5 set you can leave the existing sites using 2.0 and then start new projects in 3.5. Otherwise I recommend making a backup copy of your site on a subdomain or somewhere and then you can test your
conversion to 3.5 in safe place before pushing it to the production server. Most of the time this is not an issue, the auto conversion between 2.0 and 3.5 is just to modify your web.config to enable the 3.5 assemblies.
Mar 15, 2009 05:31 PM|djchapin|LINK
Thanks for the information, that makes alot of sense. I can definitely try it out on another website since I have another domain which isn't developed yet. I'll give it a try.