VB6 migrating to .Net with Visual Studio 2010 -


Has anyone migrated the VB6 project to Visual Studio 2010?

I have tested the migration in VS 2005, but as a result the .net code was so messy, we decided not to migrate to the net. So has the VS2010 migration wizard improved in the WS 2005 or VS 2008 wizard?

This is definitely not in 2008 and I would be very surprised if it is any different in 2010 .

VB6 and VB.net are completely different languages, and MS has never formally supported the automatic migration route beyond simple applications. The migration path is non-trivial that there are many companies around the migration services offered, I have not tried them, but my advice would be to manage it myself.

We currently have many applications which are written extensively in VB6. Our position is that the current working code has not been migrated to .net for any good reason, but all new code should be written in .net (we have actually chosen C #)

its What this means is that if we want to add a new feature to an existing VB6 app, this feature should be implemented in .net with some interop. Apps are becoming more and more frequent from time to time. Net and less and less VB We have 1 app which is just a small VB 6 component and the rest is almost completely in .net for this gradual migration approach. It has worked very well for us. Once we reach a stage where VB is less than 6 parts, then we manually convert the remaining code without the remaining cost because only a small amount is left in it.


Comments

Popular posts from this blog

c++ - Linux and clipboard -

What is expire header and how to achive them in ASP.NET and PHP? -

sql server - How can I determine which of my SQL 2005 statistics are unused? -