Debugging a custom command

Jack S wrote on 2/7/2023, 8:21 AM

@jetdv Hi Edward. I'm following your series of tutorials on building a custom command. Because I'm using VS2019, I've run into the problem you pointed out in part 3. Launching VP20 via the VS run command, there are no tabs. The tabs are there if VP is launched normally. Have you discovered why this should be with VS2019 and not with VS2015?

EDIT:- If I build the extension then install it in the extensions folder, everything is OK.
So, not so much of a problem if it only occurs at the debug stage.

Comments

jetdv wrote on 2/7/2023, 8:34 AM

@Jack S, No, I don't know why that happens. It all works fine - it's just hard to know what tab is where. If you install Visual Studio 15 and run it from there, you'll see the tabs so I'm not sure what changed between 15 and the newer versions. I have not tried newer than 2019 to see if it's still a factor with, say, VS2022.

Jack S wrote on 2/7/2023, 9:26 AM

OK, thanks. I as I say, it's not a problem as it only happens in the debug stage.

Robert Johnston wrote on 7/30/2023, 1:43 PM

@Jack S, @jetdv I managed to get the tabs to appear in Vegas Pro 19 and Visual Studio 2019 in debug mode. There is an option on the Debug properties form to "Enable native code debugging." When I enabled that, the tabs in Vegas Pro 19 appeared as usual. Then View > Extensions > CCTest was available. However, at first, the CCTest form did not appear. I fixed that problem by resetting the Windows Layout to Default (View > Windows Layouts > Default Layouts) and selecting CCTest on the Extensions menu again. Breakpoints also worked. There is quite a bit of activity loading modules and symbols before Vegas actually starts, so be patient. Look at the Output window to monitor the activity. I didn't get this extra "stuff" when Enable native code debugging was not selected. I also didn't get tabs.

No luck debugging with Vegas Pro 20 or Visual Studio 2022, although the CCTest.DLL created in Visual Studio 2019 with Vegas Pro 19 works in Vegas Pro 20.

jetdv wrote on 7/30/2023, 6:14 PM

That started with VP20. You will need to launch VEGAS first, and then attach a debugger after it has completed the initialization. It also helps to build to the VEGAS custom command folder. And the debug breakpoints will not work. This is, apparently, an intended change.

Robert Johnston wrote on 7/30/2023, 6:50 PM

@jetdv, @Jack S

I just discovered this in Visual Studio 2019 with Vegas Pro 19: Instead of "Enable native code debugging" to get the tabs to show up, I deselected that option and then went to Debug > Options > General > Use Managed Compatibility Mode. There's a message that that will be deprecated in the future.

I've been attempting to use the Attach to Process method in Visual Studio 2019 and 2022, but just don't have everything exactly as it's supposed to be. I'm going to keep trying.

Those tutorials, Edward, are extremely helpful. Thank you!