This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 33%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERM%3C/text%3E%3C/svg%3E)
I try to debug an extension for Visual Studio (2019/2022) that I wrote in C++/CLI. Now... the extension itself works. The only problem is, that I cannot jump into the code while it is executing. The breakpoints never stop. But, when I create a C# extension and derive the package from my C++/CLI package and simply override 1 function (with a function that only calls its base) and then run this extension... suddendly the breakpoints in C++/CLI start to work.
The question now is... why? (I try to do this with VS2019). Is ... I don't know...the debugger different? Is something done/modified when I load the C++/CLI code not directly but via dependency of the C# assembly? ... or is the debugging information ... modified? merged? ... why could this happen?
A high-level, general-purpose programming language, created as an extension of the C programming language, that has object-oriented, generic, and functional features in addition to facilities for low-level memory manipulation.
A cross-platform toolchain for developing, building, running, and publishing .NET applications.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(201.6, 57.00000000000001%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMY%3C/text%3E%3C/svg%3E)
Is your CLI project .NET or .NET Framework? And set Debugger type Mixed (.NET Framework/ NET Core).
it is .Net Framework 4.7.2 and the debugger type is mixed (.NET Framework) or pure .NET Framework... but I also tried the .NET Core debugger (just to be sure)
by the way... if I do derive my C# class from the C++/CLI class and do NOT override at least 1 function with this dummy "call your base class" function, then the breakpoints keep being ignored... the only way I was able to make it work was by using this inheritance and dummy-function-override idea
Can you provide the C++CLI sample and steps to create the extension project to help us reproduce your problem?
@Minxin Yu sure... I've created a sample project with the same behavior here: https://github.com/meirumeiru/BreakpointDemonstrator
the info.txt contains the needed steps to reproduce the problem
(make sure that all the assemblies that you link, come from the PublicAssemblies folder of VisualStudio and the Threading-Assembly from the PublicAssemblies\Microsoft.VisualStudio.Threading.<version> subfolder... otherwise it will not build correctly)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(118.4, 90%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EH3%3C/text%3E%3C/svg%3E)
I added Debug::WriteLine(" XXX "); In C++ CLI project. But there is no text output when InitializeAsync function is commented.
Yes... as if the whole debugging doesn't work then. But for some reason it starts working as soon as you have this 1 function in C# ... but, I've no idea how all this is linked.
Answer accepted by question author
As far as I am concerned, it's no code triggers the function, rather than no breakpoint hit.
I added the constructor and comment C# code //InitializeAsync
BreakpointDemonstratorPackage()
{
Debug::WriteLine("XXX");//break point
}
Then reach the constructor's breakpoint and output.
Also, I need to add a command item file to test the extension.
Even if the inheritance
VSIXWrapperPackage:AsyncPackage / * BreakpointDemonstrator BreakpointDemonstratorPackage * /
Without InitializeAsync, command1.cs ShowMessageBox will not trigger.
you're right... the problem is not the non hitting breakpoints in this case but that nothing get's called at all...