Debugging VB6 code in Visual Studio 2019 RRS feed

  • Question

  • Hi all.

    Does anybody know, how to debug VB6 code inside Visual Studio 2019?

    Till now I'm not successful with debugging - set Just-In-Time native, also set Use Managed Compatibility Mode (as suggested in some posts for VS2015).

    I will appreciate your help.

    Thank you.



    Monday, March 23, 2020 11:02 AM

All replies

  • Likewise as in Visual Studio 1998 (The VB6 Ide) you have first to build it (and make it error free). 

    Low chance that you succeed without major chances,  but if that happens, simply press F5 likewise in VB6.


    Monday, March 23, 2020 11:28 AM
  • Hello,

    First off I've never tried this so it may or may not work with VS2019, in the following post there was success with VS2012.


    Please remember to mark the replies as answers if they help and unmarked 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.

    NuGet BaseConnectionLibrary for database connections.

    profile for Karen Payne on Stack Exchange

    Monday, March 23, 2020 11:50 AM
  • I realize I was not precise by specifying my issues - I had a dll COM+ code, which generates an error by running in specific environment. In other environments - code is OK.

    VS2015 works ok, VS2019 is missing Use Native Compatibility mode.



    Monday, March 23, 2020 2:28 PM
  • Hi Karen.

    Thanks for help - actually Pecan (the author of mentioned question and selfanswer also)  is my coworker :).

    Unfortunately it seems to be an issue in VS2019. In VS 2015 everything works OK.

    VS2019 did not recognize symbols, even VB6 code is being compiled with symbols.

    Anyway - now I'm using VS2015 to debug it.



    Monday, March 23, 2020 2:31 PM
  • Hi David Mensik 2,

    Thanks for your feedback.

    It seems that you cannot debug VB6 in Visual Studio 2019.

    As a suggestion, try converting the VB6 code to VB.NET code.

    Besides, you can suggest a feature in Developer Community for more help.

    Hope it can help you.

    Best Regards,

    Xingyu Zhao

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, March 25, 2020 7:10 AM