Hi,

Generally when I've seen this problem, it's an installation issue. Try the removal+reinstallation fix suggested here - http://www.ncrunch.net/documentation/troubleshooting_installation-and-setup-problems. The VS2015 instructions are the same as the VS2013, but with a different VS path.

If the above sequence doesn't solve the problem for you, feel free to submit a bug report and I'll see if the log yields anything useful.

Trying to remove and reinstall actually failed the installation.
Tried to do a manual install https://www.ncrunch.net/...stallation-instructions
running devenv.exe /setup /nosetupvstemplates does not succeed.

BUT somehow the NCrunch menu has appeared in VS2017 RC Enterprise! but running ncrunch on a already existing solution, opened in VS2017, that builds in VS2017 i get the following error from NCRUNCH:
System.Exception: Unable to find a usable version of MSBuild on this machine

this did not work: www.ncrunch.net/document...ation-and-setup-problems

i went to C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE

and ran the devenv setup thing.

no ncrunch menu in vs2017

if you can provide more exact steps for 2017 (professional in my case) i will do more testing

after a reinstall I do see this folder:

C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\Remco Software\NCrunch for Visual Studio 2017

Ok, a bit of background here ...

In VS2017 MS changed the IDE so it no longer registers VS/MSBuild assemblies in the GAC. I assume this was because the GAC doesn't fit well with their new installation process.

This introduced a level of complication for products like NCrunch that need MSBuild to do processing. Microsoft also changed the installation system so that it is no longer possible to rely on the registry to find the VS installation path. All this now needs to be handled through a new COM API.

The problems described above with NCrunch reporting that it can't find VS2017 during installation and/or it cannot find a usable version of MSBuild are related to these above changes. Basically, if you see this happening it means that either you're using a version of NCrunch prior to v3.2 or the COM API isn't working as expected. Because this is all shiny new pre-release code, I'm not really confident that it's proven itself yet. If you're experiencing these problems on NCrunch v3.2 then let me know and I will help investigate further.

The problem of the NCrunch menu not appearing in a VS installation is a different one entirely. This could be happening as the result of the package failing to fully initialise itself. To troubleshoot this, we'll need a log of the VS bootstrap. Try the following:

C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\devenv.exe /vslog c:\vslog.log

Then copy/paste the contents of the c:\vslog.log file here. Hopefully it will give some clue as to why the package isn't being loaded.

Thanks! Just to confirm - the issue you have right now is that NCrunch can't find a usable version of MSBuild?

Thanks Thomas. Both of these issues actually originate from the same place. For some reason the COM API used by the NCrunch installer (and the product itself) to find the VS installation is failing. This is somewhat of a problem, because it means that this API isn't reliable in all environments and I also have no way to effectively troubleshoot it. Basically, part of your VS installation is not operating correctly.

Did the VS installation process give you an errors when it went through? Is reinstalling VS2017 an option for you?

Thanks for the log. It's interesting that there's no mention of VS even attempting to load the package.

Can you check if the extension is listed under VS's extension manager?

Noting your earlier comment about NCrunch being installed into the VS community directory, can you confirm that the NCrunch files are now existing under the correct path in a VS instance that you've run "devenv.exe /setup" with?

@Remco.
I used the msi installer for VS2017 that you provided
http://downloads.ncrunch...unch_VS2017_3.3.0.4.msi

NCrunch now works for me in VS2017 RC :)
Great.

I was curious how NCrunch stacks up agains the new Live Unit Tests in VS and NCrunch is a lot more polished, so i will continue using NCrunch :-)

NCrunch v3.3 is now formally available including a fix for this issue - https://www.ncrunch.net/download.

@EricZimmerman: Sorry, I wasn't able to isolate the issue you're experiencing. For some reason, your Visual Studio refuses to even recognise the NCrunch package and doesn't even attempt to load it. I think there may be something wrong with your VS install. Please do let me know if you manage to retrieve any more information from the process. I hope that a reinstall of VS or the VS2017 RTM will solve this for you.