0

Our VC++/C# SW product has recently migrated to a Windows 10 LTSB target. I am no longer able to see native modules in the 'Modules' tab in Visual Studio 2015 when I attach a debugger (either locally or remotely) to my managed process. I have checked the 'Enable native code debugging' in the C# project properties, and I have selected 'Managed (v4.6, v4.5, v4.0) and Native' for code type when I attach the remote debugger. I am able to debug the native code (running inside a managed process) just fine when running on the Windows 7 target.

Thanks for any help you can provide.

Nate

Nate Tater
  • 1
  • 1
  • Does it make any difference if you run Visual Studio as Admin? – Phil Brubaker Oct 10 '17 at 01:21
  • @Nate Tater, If possible, please compare the VS settings under TOOLS->Options->Debugging, or the project property, view the result. Please also mark sure that your app was in debug mode, not release mode. Of course, if you get any debug log messages, please also share it. – Jack Zhai Oct 10 '17 at 09:43
  • @Nate Tater, What about this issue? Do you get any latest information in your side? – Jack Zhai Oct 12 '17 at 02:36

1 Answers1

0

So the problem ended up being caused by McAfee Solidifier. Uninstalling this product or disabling it by calling 'sadmin disable' fixed the debugging issue.

Nate Tater
  • 1
  • 1
  • Glad to know that you have resolved this issue, you could mark your solution as the answer. Have a nice day:) – Jack Zhai Oct 16 '17 at 05:21