Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

2 Pages12>
ncrunch menu missing from vs2017
EricZimmerman
#1 Posted : Wednesday, December 21, 2016 2:41:56 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 12/6/2016(UTC)
Posts: 9
Location: United States of America

Was thanked: 1 time(s) in 1 post(s)
I have tried uninstalling and repairing an installation of 3.2 with vs2017 to no avail. i can never get the menu to show up again.

any logs or process to force it to show up again?


Microsoft Visual Studio Professional 2017 RC
Version 15.0.26014.0 D15REL
Microsoft .NET Framework
Version 4.6.01586

Installed Version: Professional

Visual Basic 2017 RC 00369-50000-00000-AA336
Microsoft Visual Basic 2017 RC

Visual C# 2017 RC 00369-50000-00000-AA336
Microsoft Visual C# 2017 RC

Common Azure Tools 1.8
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.

GitHub.VisualStudio 2.1.1.4
A Visual Studio Extension that brings the GitHub Flow into Visual Studio.

JetBrains ReSharper Ultimate 2016.3 Build 107.0.20161214.141528
JetBrains ReSharper Ultimate package for Microsoft Visual Studio. For more information about ReSharper Ultimate, visit http://www.jetbrains.com/resharper. Copyright © 2016 JetBrains, Inc.

NuGet Package Manager 4.0.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.
Remco
#2 Posted : Wednesday, December 21, 2016 10:54:27 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 4,717

Thanks: 622 times
Was thanked: 725 time(s) in 690 post(s)
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.
TLogik
#3 Posted : Wednesday, December 28, 2016 5:33:15 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 4/12/2016(UTC)
Posts: 9
Location: Denmark

Was thanked: 2 time(s) in 2 post(s)
I have the exact same problem on a vanilla VS2017RC version 15.0.26014.0
TLogik
#4 Posted : Wednesday, December 28, 2016 5:51:49 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 4/12/2016(UTC)
Posts: 9
Location: Denmark

Was thanked: 2 time(s) in 2 post(s)
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
Remco
#5 Posted : Thursday, December 29, 2016 3:37:37 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 4,717

Thanks: 622 times
Was thanked: 725 time(s) in 690 post(s)
Can you confirm that you're using the latest version of NCrunch? v3.2 introduced a very important fix targeted towards faulty installation under VS2017. The symptom's you've described are disturbingly similar to the problem that was fixed in this build.
EricZimmerman
#7 Posted : Tuesday, January 03, 2017 3:09:47 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 12/6/2016(UTC)
Posts: 9
Location: United States of America

Was thanked: 1 time(s) in 1 post(s)
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
EricZimmerman
#8 Posted : Tuesday, January 03, 2017 3:12:57 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 12/6/2016(UTC)
Posts: 9
Location: United States of America

Was thanked: 1 time(s) in 1 post(s)
Remco
#9 Posted : Tuesday, January 03, 2017 10:16:55 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 4,717

Thanks: 622 times
Was thanked: 725 time(s) in 690 post(s)
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.
TLogik
#6 Posted : Wednesday, January 04, 2017 6:16:29 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 4/12/2016(UTC)
Posts: 9
Location: Denmark

Was thanked: 2 time(s) in 2 post(s)
Remco;9640 wrote:
Can you confirm that you're using the latest version of NCrunch? v3.2 introduced a very important fix targeted towards faulty installation under VS2017. The symptom's you've described are disturbingly similar to the problem that was fixed in this build.


I am using NCrunch 3.2.0.3
[img=https://postimg.org/image/dbnry0ntl/]NCrunch Version[/img]

Edit: The image linking does not work. Image can be found here https://postimg.org/image/dbnry0ntl/
Remco
#10 Posted : Wednesday, January 04, 2017 11:26:52 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 4,717

Thanks: 622 times
Was thanked: 725 time(s) in 690 post(s)
Thanks! Just to confirm - the issue you have right now is that NCrunch can't find a usable version of MSBuild?
TLogik
#11 Posted : Wednesday, January 04, 2017 11:57:58 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 4/12/2016(UTC)
Posts: 9
Location: Denmark

Was thanked: 2 time(s) in 2 post(s)
Remco;9657 wrote:
Thanks! Just to confirm - the issue you have right now is that NCrunch can't find a usable version of MSBuild?


Well it is a two things -right.
1. The instllation did not as expected. is described earlier. Some goofing around made it work, but it is not a proper installation.
2. The NCrunch instance cannot find a usable MSBuild installation.

Essentially the MSBuild version issue should be created as a separate issue.

But i can confirm that after some work the only issue for me right now is that NCrunch cannot find a usable MSBuild version.
/Thomas
Remco
#12 Posted : Wednesday, January 04, 2017 10:58:11 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 4,717

Thanks: 622 times
Was thanked: 725 time(s) in 690 post(s)
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?
EricZimmerman
#13 Posted : Wednesday, January 04, 2017 11:09:13 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 12/6/2016(UTC)
Posts: 9
Location: United States of America

Was thanked: 1 time(s) in 1 post(s)
looks like /vslog changed to just /log

get the log here


https://cp.sync.com/dl/d...vj5ba-jqrjftsm-8ic87um5

when i install ncrunch the installer works as expected. no errors

Remco
#14 Posted : Wednesday, January 04, 2017 11:24:52 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 4,717

Thanks: 622 times
Was thanked: 725 time(s) in 690 post(s)
EricZimmerman;9661 wrote:
looks like /vslog changed to just /log

get the log here


https://cp.sync.com/dl/d...vj5ba-jqrjftsm-8ic87um5

when i install ncrunch the installer works as expected. no errors



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
#15 Posted : Thursday, January 05, 2017 1:15:01 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 4,717

Thanks: 622 times
Was thanked: 725 time(s) in 690 post(s)
TLogik
#16 Posted : Friday, January 06, 2017 4:35:24 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 4/12/2016(UTC)
Posts: 9
Location: Denmark

Was thanked: 2 time(s) in 2 post(s)
@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 :-)
1 user thanked TLogik for this useful post.
Remco on 1/6/2017(UTC)
MatthewSteeples
#17 Posted : Saturday, January 07, 2017 12:15:34 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 10/28/2014(UTC)
Posts: 38
Location: United Kingdom

Thanks: 3 times
Was thanked: 3 time(s) in 3 post(s)
3.3.0.4 fixes my installation issue on VS2017 as well
1 user thanked MatthewSteeples for this useful post.
Remco on 1/7/2017(UTC)
Remco
#18 Posted : Wednesday, January 18, 2017 11:46:37 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 4,717

Thanks: 622 times
Was thanked: 725 time(s) in 690 post(s)
NCrunch v3.3 is now formally available including a fix for this issue - https://www.ncrunch.net/download.
EricZimmerman
#19 Posted : Thursday, January 19, 2017 8:29:04 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 12/6/2016(UTC)
Posts: 9
Location: United States of America

Was thanked: 1 time(s) in 1 post(s)
Still not working for me, even after uninstalling and deleting all ncrunch stuff related to 2017. =(

ill wait til it RTMs and see if that fixes it after a reinstall of vs2017

happy to provide logs or whatever, but the new version didnt add it back to my menu at the top
Remco
#20 Posted : Thursday, January 19, 2017 10:43:36 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 4,717

Thanks: 622 times
Was thanked: 725 time(s) in 690 post(s)
@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.
Users browsing this topic
Guest
2 Pages12>
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.103 seconds.