Migrating to VB.NET soon. Question about it...

[tacoman667]

I was wondering, I use VB6 at work and we are going to migrate to .NET in the near future. I hear the migration will be a pain. Can anyone give me a brief description of the problems in recoding VB6 into vb.NET? I am looking for basically an overview of what to concentrate on when changing over my code.

Thanks a bunch!

Tacoman667

[citizenstitch]

vb.net does have an update option that will convert your old code to .net.

[tacoman667]

I tried that with a simple program I used involving classes I created with the VB6 class builder utility. The classes got all messed up in the transformation. I didn't have the time to check through it thoroughly, but it was pretty messed up and I felt I needed to completely redo my classes. Is this common from VB6 to .NET?

[techgnome]

Don't use the converter.... trust me on this, it will do two things:
1) Cause more problems than it solves.
2) IT doesn't actualy convert, but wraps the VB6 code with .NET wrappers. Example ADO.. IT doen't convert to ADO.NET, but adds the old ADO Interop reference, then simply adds Catch Trys around it and that's it.

And if you need further evidence on not using the converter, I attended a conference a couple of years ago and managed to talk to the guys that built the converter.... and even they recommended not using it. The only reason it was even built was because they knew they would hear about it if they didn't.

Based on my own experience and some of the stories I've heard, if you do convert to .NET, it's best to re-write it from scratch. It'll be cleaner, less hassle and better in the long run. Plus it gives you the chance to re-do the parts that you wish you could do all over again (that's what we are doing.)

Tg

[DaveBo]

Did you checkout the Migrating from VB6 page?
http://msdn.microsoft.com/vbasic/Lea...g/default.aspx