3,977 questions
You need to use the Mixed Debugger. For example, -
Debugging C++ CLI from MFC/C++ Breakpoints not hit, why? Settings?
![](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(316.8, 38%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMF%3C/text%3E%3C/svg%3E)
Markus Freitag
3,791
Reputation points
Hello,
nothing work.
I have a C++, CLI project and would like to debug it.
It does not work.
Checked many settings, changed them, nothing helps.
Can anyone tell me the setting?
C++ I used mixed code!
VS2019 Prof.
Later I want to use the library via C#.
MFC Client --- CLI/C++ to a C# DLL
Developer technologies | C++
Developer technologies | .NET | .NET CLI
350 questions
Accepted answer
-
RLWA32 49,551 Reputation points2022-08-08T09:28:38.93+00:00 -
Markus Freitag 3,791 Reputation points
2022-08-08T09:55:11.97+00:00 
Thanks for the quick response.
The Mixed selection is missing.Where can I display or select this?
-
RLWA32 49,551 Reputation points
2022-08-08T10:23:47.57+00:00 Customize the Standard Toolbar -
Add the Debug Type command -
After Command Added to Standard Toolbar -
Position the command (Move Down) -
-
Markus Freitag 3,791 Reputation points
2022-08-08T11:12:17.92+00:00 
I added, but it is enabled false, why?
-
RLWA32 49,551 Reputation points
2022-08-08T11:41:38.543+00:00 The example solution that I used contains 3 projects - Unmanaged C++ MFC client application, MFC DLL project with CLR support and a C# class library.
Make sure your startup project is set to the Unmanaged C++ MFC client application.
-
Markus Freitag 3,791 Reputation points
2022-08-08T11:58:40.313+00:00 
I did this, I did that.
I can debug in via the MFC client into the C# DLL.
This works. I just can't debug the library.Can you upload your test project. What could be the cause. Probably some compiler settings.
-
RLWA32 49,551 Reputation points
2022-08-08T12:40:15.44+00:00 By the way, in these types of mixed projects the debugger breakpoints in the MFC DLL and the C# assembly will not be shown as enabled when the unmanaged C++ MFC Client is first started. After the CLR loads the MFC C++/CLI DLL its breakpoint will become enabled and after the C# class library loads then the C# breakpoint will become enabled.
Have you actually tried running the code to see if the breakpoints are hit?
-
Markus Freitag 3,791 Reputation points
2022-08-08T12:51:43.53+00:00 
Works well, only inside the Library. Maybe is not possible. Can you check your project please.
It also works without debugging. If there is a possibility it would be easier for adjustments and debugging.
You have helped me before. Thanks again. Maybe you have another tip. -
RLWA32 49,551 Reputation points
2022-08-08T13:03:25.407+00:00 My example solution is on Onedrive -- https://1drv.ms/u/s!AmnqrCFBv4nDgj8QFPe-mMAJmRs1?e=fUpoAe
-
RLWA32 49,551 Reputation points
2022-08-08T13:24:02.6+00:00 Another thought - The project property for Debugger Type is configured for each individual combination of Configuration/Platform. So in the project property page set it to desired type of Mixed debugger for All Configurations/All Platforms.
-
Markus Freitag 3,791 Reputation points
2022-08-08T13:24:55.03+00:00 Thanks, your sample works well.
I found differences. Do you know it? How I can add more debugger types?
I have an old project and it must be in VS2010.
There it does not work, if I switch to 2019 it works.
When I debug I have to take care of it.Do you know a solution for 2010.
If not we can end the thread. Thanks for your test project, your help! -
RLWA32 49,551 Reputation points
2022-08-08T13:42:30.39+00:00 I have an old project and it must be in VS2010.
There it does not work, if I switch to 2019 it works.Do you mean you are building in VS2019 but using the toolset from VS2010?
If so, I can't help you as I don't have VS2019 and VS2010 installed on the same system.
-
Markus Freitag 3,791 Reputation points
2022-08-08T13:50:22.613+00:00 Yes, right. Because the Client is in VS2010.
No one has updated it. Good, I know the cause now. I will create a TestApp, if it works then I will switch to 2010 and create the whole project. Yes, if you know, cost a lot of time again. Thank you!
Sign in to comment -