Patrick Kelly

[ILVerify](https://github.com/dotnet/corert/tree/master/src/ILVerify/) replaces PEVerify, and is apparently managed and cross platform code. Someone needs to find a way to reliably retrieve an executable. A nuget package containing it would be ideal....

Upon further testing it seems like this happens regardless of the project type. Moreso, building projects inside Visual Studio causes Visual Studio to report the following error. ~~~~ The command...

Okay thanks, this sets me on the right path, so I can look into it as well.

I found these `$(Win10SDKBinPath)` `$(Win10SDKVersion)` which I'm pretty sure are the correct variables. I'll play around with getting this to work tomorrow.

Apparently I misunderstood what I was looking at. Those were locally created variables, that were filled in by looking for a specific registry key (which of course doesn't exist anymore...

In that thread there was this: [dotnet-ildasm](https://github.com/pjbgf/dotnet-ildasm) which might abstract away a lot of the complexities of getting the right tool.

I completely understand that. I'll look into the nuget packages and where they dump their contents.

And that approach should work for any platform. Perfect. I'll play around with it.

Here's where I'm at. **Microsoft.NETCore.ILDasm** doesn't seem to actually contain anything remotely useful.  And in fact nothing useful is pulled down when a restore occurs  Which then requires...

 Path resolution looks okay on Windows. I'll look into ways to deal with the library.