Yes, They are the same.

This is related to the new C++ Just My Code Stepping (JMC) feature in Visual Studio 2017 15.8. Because the feature depends on CRT (C Run-Time Libraries), if the project does not link to CRT, it may hit "error LNK2019: unresolved external symbol __CheckForDebuggerJustMyCode". The workaround is to disable JMC: Method 1: in project setting, "Configuration Properties" -> "C/C++" -> "General": "Support Just My Code Debugging". Change to NO. Method 2:add /JMC- to compiler option, specifically. Etc, in project setting, add /JMC- to "Configuration Properties" -> "C/C++" -> "Command line" -> "Additional Options"

The root cause is very clear now, as this JMC is only for C++ project with CRT, we shouldn't blindly enabled this for all C++ projects. For Windows driver project, the "Runtime Library" option in "C/C++ -> Code Generation" is blank by default, we absolutely shouldn't enable the JMC switch for this kind of project.

This issue has been fixed and is now available in our latest update. You can download the update via the in-product notification or from here: https://visualstudio.microsoft.com/vs/ Thanks to everyone who provided feedback, votes and solutions for this problem.

any sln like this error

昨天升级到Visual Studio 2017 15.8.

今天编译个驱动,也遇到这个问题.

估计是这个驱动用了一些用户态的头文件．

每个ＯＢＪ文件都出现了：error LNK2001: 无法解析的外部符号 __CheckForDebuggerJustMyCode

诚如上面所说：

Method 1: in project setting, "Configuration Properties" -> "C/C++" -> "General": "Support Just My Code Debugging". Change to NO.

用这个办法解决了．

https://correy.webs.com