none
Convert VB6 to VB.Net

    Question

  • Hi!

    I'm considering converting a vb6-program to VB.Net.

    However I'm not quite sure whether or not it's a good idea.

    The program is being used a lot by several users and is re-developed (new features, etc.) often.

    The idea behind converting it, is to make the program more "future-safe".

    Does anybody have experience/good advice regarding this?

    Monday, April 11, 2011 9:36 AM

Answers

    • Marked as answer by Sapphire888 Tuesday, April 12, 2011 1:46 PM
    Monday, April 11, 2011 9:42 AM
  • Sapphire,

    The trouble with VB6 programs you describe is, that the VB6 part is just the main and for the rest it is created with all kind of Win32 Dll's and 3th party tools which have no support anymore. 

    For that are currently no tools to convert.

    "future safe" does not exist, but because of the current high efforts the Microsoft .Net development team puts on making VB again that language which it was in the world, is there a chance that by going to VB 10 you are on the right track. For the rest has it the same future safe guarantees as every program or OS system. If there is tomorrow a newer one which is really better (not better because it is easier to do for those who have long time VB experience), than that one will have the future. I've not seen it yet. 

    The language of VB10 is still the same as with VB6 with some small improvements to make it more stable and reliable on the long term. 

    However, all those things done with classic Ado, Win32 Dll's and found 3th party tools, have to be replaced and then converting makes seldom sense.

    However, if you use the old program as the goal for what it should at least do, than you can often use a lot of the original code, but that is than copy and past.

     


    Success
    Cor




    • Marked as answer by Sapphire888 Tuesday, April 12, 2011 1:46 PM
    Monday, April 11, 2011 10:49 AM
  • As a VB 6.0 app it is definitely not future safe. Future versions of Windows (after version 7) may not support it. If you anticipate the app being in production beyond the next 10 years you may want to consider upgrading to Visual Basic .NET.

    BTW, you may want to try the trial version of Artinsoft's Visual Basic Upgrade Companion as it will allow you to convert up to 10,000 lines of code.


    Paul ~~~~ Microsoft MVP (Visual Basic)
    • Marked as answer by Sapphire888 Tuesday, April 12, 2011 1:46 PM
    Monday, April 11, 2011 1:56 PM
  • COmpletely agree with all comments here.

    VB6 is definately old technology with IDE not supported from Win7 onwards.   So making any changes requires staying on older OS's.   This could cause problems in the future.

    VB.NET is similar syntax to older VB language - albiet there are changes which cn significantly improve reliability and reduce code count.    Examples of this are type safe collections with Generics.  Reduced code with Auto Implemented Properties, Collection and Array Initializers, LINQ, Lambda's, XML Literals etc.

    So redeveloping you application can involve upgrading the code uping a tool such as ArtinSoft tool and then refactoring your code.   This allows you to simplify and cleanup code.

    Ultimately once youve done the conversion to .NET then you'll be in a better position to maintain this app into the future.    VB.NET is definately a language that is continuing to develop and the key thing here is that the language is simplifying common tasks reducing code complexity.

    Ultimately VB6 is not a sustainable technology for future development.   If you application is static then upgrading may not be an option, but if it is still undergoing enhancements then upgrading to .NET is definately the way forward.

     

    • Marked as answer by Sapphire888 Tuesday, April 12, 2011 1:46 PM
    Monday, April 11, 2011 3:40 PM

All replies

    • Marked as answer by Sapphire888 Tuesday, April 12, 2011 1:46 PM
    Monday, April 11, 2011 9:42 AM
  • Sapphire,

    The trouble with VB6 programs you describe is, that the VB6 part is just the main and for the rest it is created with all kind of Win32 Dll's and 3th party tools which have no support anymore. 

    For that are currently no tools to convert.

    "future safe" does not exist, but because of the current high efforts the Microsoft .Net development team puts on making VB again that language which it was in the world, is there a chance that by going to VB 10 you are on the right track. For the rest has it the same future safe guarantees as every program or OS system. If there is tomorrow a newer one which is really better (not better because it is easier to do for those who have long time VB experience), than that one will have the future. I've not seen it yet. 

    The language of VB10 is still the same as with VB6 with some small improvements to make it more stable and reliable on the long term. 

    However, all those things done with classic Ado, Win32 Dll's and found 3th party tools, have to be replaced and then converting makes seldom sense.

    However, if you use the old program as the goal for what it should at least do, than you can often use a lot of the original code, but that is than copy and past.

     


    Success
    Cor




    • Marked as answer by Sapphire888 Tuesday, April 12, 2011 1:46 PM
    Monday, April 11, 2011 10:49 AM
  • As a VB 6.0 app it is definitely not future safe. Future versions of Windows (after version 7) may not support it. If you anticipate the app being in production beyond the next 10 years you may want to consider upgrading to Visual Basic .NET.

    BTW, you may want to try the trial version of Artinsoft's Visual Basic Upgrade Companion as it will allow you to convert up to 10,000 lines of code.


    Paul ~~~~ Microsoft MVP (Visual Basic)
    • Marked as answer by Sapphire888 Tuesday, April 12, 2011 1:46 PM
    Monday, April 11, 2011 1:56 PM
  • COmpletely agree with all comments here.

    VB6 is definately old technology with IDE not supported from Win7 onwards.   So making any changes requires staying on older OS's.   This could cause problems in the future.

    VB.NET is similar syntax to older VB language - albiet there are changes which cn significantly improve reliability and reduce code count.    Examples of this are type safe collections with Generics.  Reduced code with Auto Implemented Properties, Collection and Array Initializers, LINQ, Lambda's, XML Literals etc.

    So redeveloping you application can involve upgrading the code uping a tool such as ArtinSoft tool and then refactoring your code.   This allows you to simplify and cleanup code.

    Ultimately once youve done the conversion to .NET then you'll be in a better position to maintain this app into the future.    VB.NET is definately a language that is continuing to develop and the key thing here is that the language is simplifying common tasks reducing code complexity.

    Ultimately VB6 is not a sustainable technology for future development.   If you application is static then upgrading may not be an option, but if it is still undergoing enhancements then upgrading to .NET is definately the way forward.

     

    • Marked as answer by Sapphire888 Tuesday, April 12, 2011 1:46 PM
    Monday, April 11, 2011 3:40 PM
  • Thank You all for Your answers! -> I appreciate Your input very much :o)

    Best regards...

    Sapphire888

     

    Tuesday, April 12, 2011 1:45 PM