Forum member

omusavi

9 posts

Posts by omusavi

  1. NCrunch unable to find sn.exe (VS2017 only)

    Just a quick follow-up, we updated our VSTS agents to use 3.14 and this error is fixed, I am guessing through the path search. Thanks so much for taking a look and glad the fix worked!

    22 Mar 2018 18:45 UTC

  2. NCrunch unable to find sn.exe (VS2017 only)

    Thanks for the info, I am going to investigate to see what is happening on our machines that is placing the SDKs in a different location and will let you know what I find!

    22 Feb 2018 18:55 UTC

  3. NCrunch unable to find sn.exe (VS2017 only)

    Got the following error with the build: System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Program Files\Microsoft SDKs\Windows'. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileSystemEnumerableIterator`1.CommonInit() at S…

    21 Feb 2018 23:18 UTC

  4. NCrunch unable to find sn.exe (VS2017 only)

    Thanks, I will try it with the build and let you know how it goes. In the meantime, any ideas why even setting the registry values didn't work as a workaround? On a clean Windows 10 machine with only VS2017 installed, are you guys getting different values than I am for the windows SDK paths?

    21 Feb 2018 23:15 UTC

  5. NCrunch unable to find sn.exe (VS2017 only)

    Upon further investigation, I think you are right that something different is happening here. I created a new key to one that was previously indicated was searched (HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Microsoft SDKs\Windows\v8.0\), set the InstallationFolder to a known directory that h…

    21 Feb 2018 18:50 UTC

  6. NCrunch unable to find sn.exe (VS2017 only)

    We are seeing this on machines that we configure as VSTS Build Agents and I was able to repro locally on a clean machine (imaged last week) with Windows 10 and VS2017 installed (no previous VS installed). My other machine that had VS2015 on it previously works fine with the exact same project Cop…

    20 Feb 2018 23:54 UTC

  7. NCrunch unable to find sn.exe (VS2017 only)

    Hey Remco, We are seeing an issue where machines that only have VS2017 installed are hitting an error where they cannot find sn.exe: NCrunch was unable to find sn.exe for re-signing an instrumented assembly. Please ensure you have the Windows SDK or Visual Studio installed on the system buildin…

    20 Feb 2018 22:13 UTC

  8. Temporarily disable NCrunch from command line?

    Thanks Remco, I will add that to the uservoice!

    13 Feb 2017 22:55 UTC

  9. Temporarily disable NCrunch from command line?

    Hey Remco, We have a bunch of build scripts that run that can do builds outside of the visual studio process, sometimes having NCrunch running can cause problems with those since it is watching the directories. I was wondering if there is any way to programmatically disable and then re-enable NCrun…

    13 Feb 2017 22:17 UTC