Just one word of caution - it will actually be a rewrite rather than a
conversion. VB.Net is a different beastie to VB6, and they differ in so
many small but significant ways that you will need to go through each line
of code to ensure that it still does what you want it to do.
VS comes with an upgrade wizard. Just open the VB6 project in VS and it
will pop up automatically.
However, as VB.NET is not just a new version of Classic VB, migration
between the two programming languages is not a straightforward process.
Often a complete rewrite is the preferable solution. There are some
(commercial) tools available which will assist conversion:
I would strongly urge that you do not use the conversion wizard to
convert your VB project. In my opinion the conversion wizard is one of
the main reason VB.NET has such a negative stigma around it.
Instead I would recommend you treat this upgrade like you would an
upgrade to any other language, such as C#, C++, or Java, do a complete
rewrite, starting from scratch.
Basically, if you try to treat VB.NET like you would VB, it will come
back and bite you.
Its based on v2005, because that (and various versions of VB Classic) is all
that I use. But unless the changes in 2008 include things such as
determinalistic finalisation, I can't see that it will make any differences.
Oh, and BTW, I have done some simple "upgrades" of fully functioning VB6
code, and some of the small differences between Classic and .NET do make a
big difference...
Thanks, because I had only done this with VB2002 and that was bad.
I can use those links you have send me.
Cor
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.