Visual Studio 2017 WDK 10 Extension

NTDEV
1

I have two Windows hosts where I install the latest Visual Studio 2017
15.8.2. I then install WDK 1803. I follow Microsoft’s instructions from
this site:

https://docs.microsoft.com/en-us/windows-hardware/drivers/download-the-wdk

After the installation of the WDK, I get the “Welcome to the Windows Driver
Kit - Windows 10.0.17134.1!” prompt. Host A only gives the “Learn more
about the Windows Driver Kit” checkbox. Host B provides that option along
with the “Install Windows Driver Kit Visual Studio extension” checkbox. The
only difference between the two is that Host A has VS2013, VS2015, and
VS2017 installed on it. Host A has also gone through uninstall and
reinstall of VS2017 and the WDK as I try to resolve multiple issues. Now
Host A is in a state where the extension option doesn’t appear even though
VS2017 is installed.

Does anyone know why the VS extension option would not appear when
installing the WDK? What is the recommended way to install it manually?
Thank you.

Mike

2

Regarding my previous e-mail where I wrote:

Does anyone know why the VS extension option would not appear when
installing the WDK? What is the recommended way to install it manually?

I found that Host B had a “C:\Program Files (x86)\Windows Kits\10\Vsix”
folder where Host A did not. So I manually copied that folder from Host B
to Host A and ran WDK.vsix. That enabled the VS2017 WDK extension. Now
when loading up a driver in VS2017, it reports that
“ValidateNTTargetVersion” task could not be loaded from the assembly. It’s
looking for Microsoft.DriverKit.Build.Tasks.15.0.dll. That file is present
on Host B but not on Host A. Next step is to copy the entire “C:\Program
Files (x86)\Windows Kits\10\build” folder from Host B to Host A. Now I can
build the driver in VS2017 but it fails in the link phase due to
“__CheckForDebuggerJustMyCode”. Thanks to Peter’s blog, I disabled Just My
Code Debugging (in the project property pages) and now the driver builds.

Mike