VS15 Installer

Hi Remco,

Do you have any plans to create an installer for VS15 yet? Even if it's just provided 'as-is'. I understand it's only at the preview stage and not officially supported etc.

Regards,
Matthew

Hi Matthew,

No plans at the moment. Right now it's still too early to look into integrating with VS15. I'll re-evaluate this when it reaches RC status.

Thanks for letting us know

Bump, it reached RC status :)

DeltaEngine wrote:Bump, it reached RC status :)

Now a work in progress :)

Now released :)

http://blog.ncrunch.net/post/Announcing-NCrunch-Version-3!.aspx.

Hi Remco,

I don't seem to be getting NCrunch in the Enterprise 2017 RC.

Running 15.0.25928.0 and it's definitely installed, and I tried a repair to no avail.

It looks like it always installs to
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\Extensions

which is an otherwise empty path as I don't have Professional installed

rather than
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\Extensions

---

EDIT: Copying the Remco Software folder over didn't seem to work either. It appears in the Extensions window, but no NCrunch menu option.

EDIT 2: Following the step
Using a command prompt or run dialog, execute the following command: C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\devenv.exe /setup /nosetupvstemplates

After copying seems to get it working.

EDIT 3: Got the menu item but can't enable NCrunch with either the menu or hotkey :)

The VS2017 installer is a bit different to that of the other versions of VS. MS changed the whole install system behind VS, so the tried and tested methods of finding the VS installation no longer work. It looks like the registry key I was using as a fallback isn't reliable either.

Is it possible you installed the professional version first, then later replaced it with the enterprise version?

In your registry, look for the value:

KHLM\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\SxS\VS7\15.0

You'll probably find that this is pointing at the non-existing 'Professional' path. Try changing this to:

C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\

This should fix the installer, and it may very well fix the problem with the engine not enabling properly.

Remco wrote:Is it possible you installed the professional version first, then later replaced it with the enterprise version?

I thought it may be related to something like that. I did stop the Pro installation halfway to install Enterprise, looks like the installer didn't clean up the registry keys correctly.

Uninstalled NCrunch and removed the folder I previously copied.
Did what you said re: registry key, installed NCrunch again and this time it went to the Enterprise directory.

When I start VS up again I have the menu item correctly, but still can't start NCrunch.

Here's what happens:
[img=https://i.imgur.com/Ws3Yps8.png]Hotkey[/img]

[img=https://i.imgur.com/OirEj0z.png]Menu[/img]

Would you be able to submit a bug report after opening a solution? Most likely there'll be something reported in the log we can use to identify the problem.

Remco wrote:Would you be able to submit a bug report after opening a solution? Most likely there'll be something reported in the log we can use to identify the problem.

Done. There is an error in there about not having Framework462, so I will try installing that and see if it helps.

Thanks! I just saw that in the report. How is it that you managed to install VS2017 without .NET 4.6.2? I had thought it was a dependency. Which version of .NET is installed on your machine?

Remco wrote:Thanks! I just saw that in the report. How is it that you managed to install VS2017 without .NET 4.6.2? I had thought it was a dependency. Which version of .NET is installed on your machine?

No clue, it could be related to my aforementioned stopping the installer halfway during the Pro installation. I have 4.6.1 installed.

jschreuder wrote:
No clue, it could be related to my aforementioned stopping the installer halfway during the Pro installation. I have 4.6.1 installed.

That's extremely interesting. So VS2017 can work with 4.6.1 OR 4.6.2, and it doesn't automatically install the latest version.

There's new surprises with every version of VS :)

I'm making a change to NCrunch to switch to 4.6.1 where 4.6.2 doesn't exist. This will be included in the 3.1 release expected out in a day or so. Meanwhile, I'm fairly certain that installing 4.6.2 will solve your problem.

Remco wrote:
That's extremely interesting. So VS2017 can work with 4.6.1 OR 4.6.2, and it doesn't automatically install the latest version.

I have no idea if it is supposed to automatically install 4.6.2 :)

You are right, it seems to be working after installing it. Thanks for your help!

Just found another issue, not sure if you can workaround, but if the new lightweight solution load kicks in, NCrunch fails to load projects. I just sent you a bug report before working out why.

To resolve, I can right click the solution in Solution Explorer and go to Properties. This seems to kick it out of lightweight mode and NCrunch can load the projects correctly.

Thanks, I saw your report come through.

The new lightweight system works on a whole new project model inside VS. If I understand this model correctly, VS basically doesn't load projects until it absolutely needs to. I presume the rationale here is that big solutions will be full of projects that probably don't all need to be loaded at any one time, so keeping a number of them unloaded helps with performance.

The problem is that unless a project is loaded by VS, it isn't visible to NCrunch. So NCrunch ends up waiting forever for a project that is declared in the solution file but not reported by the IDE.

Unfortunately, because the system is still so new, there isn't any documentation available yet about how it works or how to integrate with it. I'm pushing for more information from Microsoft, but it may take a while to get it worked out.

So for the time being, I think I'll just need to go and say it: Lightweight mode isn't supported yet by NCrunch. If you want to use NCrunch with VS2017, make sure you have this disabled in your VS options.

Makes sense to me. Even Microsoft says "there is no workaround" for extensions not behaving as expected.

Just thought I'd call it out here just in case someone else runs into the issue.

jschreuder wrote:
Just thought I'd call it out here just in case someone else runs into the issue.

You also made me aware of the problem. I didn't know it existed yet :)

Do keep reporting these problems as you find them. The quicker I can get them fixed, the less frustration there will be for everyone.

Haha no worries.

Next issue in the process... most projects are loading but a few are not. I sent a bug report in but the gist is:

The "TransformXml" task could not be instantiated from the assembly "C:\Users\me\AppData\Local\NCrunch\16876\17\MyProj\packages\MSBuild.Microsoft.VisualStudio.Web.targets.14.0.0\tools\VSToolsPath\Web\Microsoft.Web.Publishing.Tasks.dll". Please verify the task assembly has been built using the same version of the Microsoft.Build.Framework assembly as the one installed on your computer and that your host application is not missing a binding redirect for Microsoft.Build.Framework. Unable to cast object of type 'Microsoft.Web.Publishing.Tasks.TransformXml' to type 'Microsoft.Build.Framework.ITask'.
The "TransformXml" task has been declared or used incorrectly, or failed during construction. Check the spelling of the task name and the assembly name.

The same project works fine on VS 2015.

It also builds fine with the normal VS build. Seems tied to NCrunch's build somehow.