This week I’m going to try and start the move from Windows XP to Windows 7 on my development PC at work. I’ve downloaded the Windows Easy Transfer app for going from XP to Win7; that should take care of My Documents. My concern is all of the development environment. In particular I’m concerned about re-establishing things like my Windows services, which host my WCG services, etc. They use TCP and various ports. Plus there are the various ASP.NET apps that are on my machine. What caveats should I be aware of, before I start this?
+13
A:
I deeply don't recommend you to migrate. If I were you, I'd backup these files, format the PC, reinstall everything back again and re-set up the websites. No matter how much pain that may cause, it's still less pain then the potential one you might get if you use this migration tool rather than doing it properly, which would eventually cause you to do the right way anyway.
MarceloRamires
2010-03-09 20:33:31
+100. Reformat and install it. You'll be happier, and so will those around you.
Adam Robinson
2010-03-09 20:35:17
Agree with these smart guys. You could also just back it up, and install slackware. :V
cazlab
2010-03-09 20:44:36
I did this just last week and would also recommend a clean install. I didn't do a clean install on one of my computers and small irritating permissions and file ownership bugs popped up. There are also differences between IIS 6 and IIS 7 that will need to be overcome anyway, so best just do it from scratch.
Jason
2010-03-09 22:07:47
The Easy transfer tool works well for the typical average home user. It will transfer your user profile correctly, but that that's about it.
Jesse Weigert
2010-03-09 23:36:55
You are correct, I will wipe my machine clean and install the OS that way, rather than try to do an upgrade.What are the issues involved going from IIS 6 to IIS7?
Rod
2010-03-10 17:19:45
Clean install is the way to go! +1
bLee
2010-03-10 20:24:44
A:
Not to be too cynical, but perhaps you should ask the ever-helpful folks at Microsoft why they are continually producing operating environments that are so vastly superior to their previous one that you simply gotta have it, but then force you to tear down and rebuild the structure that is the reason you have that environment in the first place every time...
Really. If they appreciate at all that independent developers contribute to their growth, they could think this through a bit more carefully.
Addendum: OK, I let my frustration with MS creep through in my tone and deserve the down vote.
Nevertheless, if you strip out the attitude problem, I thought this was both a legitimate criticism and a valid, perhaps even helpful suggestion. Maybe if MS gets enough feedback questions like this will no longer need to be asked?
Of course if you already believe that MS will simply never listen to their developer customers, and that no amount of suggestions and requests for improvement will have any effect, then my answer comes across as mere venting - but believe it or not that was not my intention.
mickeyf
2010-03-10 15:34:02
1: MS listens to their devs more then any other major vendor out there. 2: "Forcing" people to upgrade once a decade is dramatically less then what you would experience on any other OS.
Matt Briggs
2010-03-10 20:21:13
I believe only way to avoid your problem is never making a new operating system. Your problem doesn't only exist with Windows, but it also does for other platform, even all the different unix distros.
bLee
2010-03-10 20:22:44