Converting vb6 projects RRS feed

All replies

  • You mean a clean VB6 project without all kind of additions to keep it in the presentation style of today?

    That is possible, otherwise, forget it. You can make from it classes which helps but the rest you have to do new. 


    Monday, May 14, 2018 10:07 AM
  • In general the best course of action is to not do a conversion but instead create a new solution in Visual Studio 2017. The reasoning behind this is that even after a conversation you still have a VB6 solution as the base as a converter does not use not up to date files but the old files and there has been many changes to base files between VB6 and VB.NET or C#.

    But if you must do a conversion from your current VB6 solution.

    • Make a complete backup of your project before starting any work.
    • If there are third party controls (especially COM based) be prepared to find replacements as they tend not to work under .NET projects.
    • Download Code Advisor for Visual Basic 6.
    • Use the following forum for assistance which is dedicated to VB6.

    Please remember to mark the replies as answers if they help and unmark them if they provide no help, this will help others who are looking for solutions to the same or similar problem. Contact via my Twitter (Karen Payne) or Facebook (Karen Payne) via my MSDN profile but will not answer coding question on either.
    VB Forums - moderator
    profile for Karen Payne on Stack Exchange, a network of free, community-driven Q&A sites

    Monday, May 14, 2018 10:38 AM
  • Frequently Answered Question.

    1. It is easier to re write your program (if its large and complex) using the new .net way.

    Although old vb6 code can be cut and paste into the new .net project shell without changes in many cases, other things like gosub, file handling, some controls, variable types, and graphics need to be re-written from scratch so its best to just to start doing it.

    It is not converting vb6, it is starting over with and re-using what chunks you can from the past.

    Now you can finally restructure your code, the way you always wanted to, but did not, because it would be too hard.

    Now you have no choice so you might as well do a good job while you are at it.

    It takes time but you will be very happy with the results. Do a good job with the rewrite then you can do much more. Finally be rid of that old nightmare that no longer runs.

    PS Here are somethings to start with:

    Monday, May 14, 2018 1:29 PM
  • FAQ on converting visual basic 6

    Not really clear what it is you are asking.

    But as others have said here, it isn't really practical to convert VB6 to any of the flavors of VB.Net.  VB6 and VB.Net are considerably different.

    If you must 'convert' then the best way is to rewrite the application from scratch.  Which at least means you can choose the language you would prefer to use.

    If all you want to do is update the look and feel of your existing VB6 program, you can simply add a manifest to the app to do this - and this is usually just a couple of minutes work. Much easier than rewriting the entire program.

    Microsoft say they will support VB6 for at least the lifetime of Windows 10 and Windows Server 2016.

    Microsoft support VB6 programming (VB6 Support Statement, VB6 Programming IDE Installer)

    Thursday, May 17, 2018 3:57 PM

  • But as others have said here, it isn't really practical to convert VB6 to any of the flavors of VB.Net.  VB6 and VB.Net are considerably different.

    Current VB15 is less different from VB6 than version VB6 from VB version1.

    Be aware that VB.Net (VB7) does not exist anymore. Current VB is VB15 which is not solely available as was version 6 outside Visual Studio 1998. 

    Also be aware that the runtime VB6 SP6 is supported (as it is), not the stripped version of Visual Studio 1998 which was available as package with VB6.


    Thursday, May 17, 2018 4:15 PM