When updating NCrunch from 3.7.0.7 to 3.11.0.9, on Visual Studio 2017 Community 15.4.3, the installer put it to:
C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\Common7\IDE\Extensions
Of course Visual Studio didn't find it there, so everything went wrong (extension could not be found, activitylog.xml refers to old directory from 3.7.0.7, followed the instructions in the forum including devenv.exe /setup, now everything's gone, no ncrunch menu at all, and so on). Only a manual installation to
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions
could fix it. So everything's fine now, for me the problem is solved, but I'm not sure why this happened and whether the installer should be fixed.
Setup Problems
3.11.0.9 not working: Installs to VS 2017 Buildtools directory
Started by mc-clasoft on 5,770 views
Remco NCrunch Developer
#11486
12 Nov 2017 21:56 UTC
Hi, thanks for sharing this issue.
This is a known problem caused by the limitations of the MSI installer. See here for other reports - http://forum.ncrunch.net/yaf_postst2272_Installing-NCrunch-on-nicknamed-multiple-installations-of-Visual-Studio-2017.aspx. We're aware of it and hope to eventually resolve it, but for now if you have multiple VS2017 instances installed, you'll need to install NCrunch manually.
Apparently the build tools is considered by the system to be a different instance of VS2017, so the installer considers it a candidate for installation.
This is a known problem caused by the limitations of the MSI installer. See here for other reports - http://forum.ncrunch.net/yaf_postst2272_Installing-NCrunch-on-nicknamed-multiple-installations-of-Visual-Studio-2017.aspx. We're aware of it and hope to eventually resolve it, but for now if you have multiple VS2017 instances installed, you'll need to install NCrunch manually.
Apparently the build tools is considered by the system to be a different instance of VS2017, so the installer considers it a candidate for installation.
Post a reply
Log in to reply.