Migration to Studio 2005

This whole episode of code synchronization (refer to previous blogs) actually made me start thinking about migration once. And I looked up the msdn and googled for it. The interesting thing is that I didn't find anything significant on Migration strategies to 2005. There is one age old article at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/cominterop.asp that compares migration and interop and says some things about migration strategies if you are migrating from classic to .net.

But there is nothing specific to Studio 2005. Something that addresses issues like how much effort is required. Or what kind of efforts would need to be put into it. Or hardware requirements or Specific strategies or issues that need to be considered during the migration or usual pitfalls and gotchas that are encountered during a migration.

I think I should take this seriously and kinda host a report on migration. Something that can be referred to, whenever someone is planning a migration to 2005. Might be helpful. Could make it a technology change proposal and propose it at my workplace... Might get me a promotion.