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.