none
Visual Basic - VB6 relative performance

    Question

  • VS 2015 Pro running on Windows10.

    A 5000 line VS - Visual Basic application runs 10 times slower  than the VB6 version !!!

    Does anyone know why ?

    Saturday, July 23, 2016 6:14 PM

Answers

  • Remember VB.Net and VB6 are different languages. VB.Net is closer to C# than it is to VB6.

    If you have just converted an existing VB6 program, either entirely manually or with a migration wizard, it is likely to be slower than VB6.

    Refactoring may help you get the performance closer to that of VB6. 

    Otherwise you need to identify the parts of your VB.Net code that are slow and re-write them.

    A lot will depend on exactly what your application is trying to do.

    Generally speaking, if you have to migrate from the VB6 programming language it is better to re-write the app in your chosen language rather than use a migration tool. It isn't an easy task, which is why Microsoft still support VB6 until at least 2025.

     


    Microsoft VB6 programming support statement: https://msdn.microsoft.com/en-us/vstudio/ms788708.aspx


    Monday, July 25, 2016 1:46 PM

All replies

  • Hi Greg Yorke,

    Thanks for your post.

    >>Visual Basic application runs 10 times slower  than the VB6 version !!!

    Was the VB application developed in VB6 version? Currently we don't support VB6 version.

    If the VB application was created in VB6. There might be some compatibility issues in VS2015. And it might cause the performance in VS2015 as well.

    So please try to create a new project in VS2015 then re-develop your application.

    In addition, if possible, please share us a your VB application then we could reproduce the performance issue in our sides then we could better troubleshoot your issue.

    Thanks for your understanding.

    Best Regards,

    Lake Xiao

    Monday, July 25, 2016 6:17 AM
    Moderator
  • Remember VB.Net and VB6 are different languages. VB.Net is closer to C# than it is to VB6.

    If you have just converted an existing VB6 program, either entirely manually or with a migration wizard, it is likely to be slower than VB6.

    Refactoring may help you get the performance closer to that of VB6. 

    Otherwise you need to identify the parts of your VB.Net code that are slow and re-write them.

    A lot will depend on exactly what your application is trying to do.

    Generally speaking, if you have to migrate from the VB6 programming language it is better to re-write the app in your chosen language rather than use a migration tool. It isn't an easy task, which is why Microsoft still support VB6 until at least 2025.

     


    Microsoft VB6 programming support statement: https://msdn.microsoft.com/en-us/vstudio/ms788708.aspx


    Monday, July 25, 2016 1:46 PM