I had the exact same issue. To confirm, look in the call stack at ac# stack frame. For me it said C++ instead of C#. For anyone else with this problem:
I fixed it by looking at the compatibility settings for VSLauncher.exe, Devenv.exe, and the shortcut to Devenv.exe. One of them (VSLauncher.exe) has compatibility mode set to Windows XP. I turned that off and it was fixed.
The Hex display is because you chose that option (clicked on the toolbar), click on it again to switch back to the normal display. The C++/CLI type is not related to the Hex dispaly issue though.
I ran into this issue as well, the debugger picked up c# and c++ in all c# projects. I'm running windows 7 64 bit.
I resolved this issue by going to the compatibility tab of the properties of the shortcut. It was checked as running as windows xp service pack 3. I unchecked that and still kept run as administrator checked. Suddenly my debugger picked all of it up as c# again.
I solved the issue by re-installing the OS. But I do remember that i was installing lot of software while i was installing the Visual Studio that. might have corrupted the OS file
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.