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

Notification

Icon
Error

Two instances of VS2017 installed, NCrunch only install into one
johnmwright
#1 Posted : Monday, June 12, 2017 2:12:15 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 9/27/2011(UTC)
Posts: 43
Location: Chicago, IL

Thanks: 2 times
Was thanked: 7 time(s) in 6 post(s)
I installed VS2017 Pro, then later got access to VS2017 Enterprise. Since there isn't an upgrade path between the two, the installer will install Enterprise into a different folder, thus allowing side-by-side installations of the two SKUs.

VS2017 Pro is installed into "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\devenv.exe"
VS2017 Ent is installed into "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\devenv.exe"

I uninstalled and reinstalled NCrunch VS2017 3.9.0.1, but it only is enabled in VS2017 Pro and is not available in VS2017 Enterprise.

Within Visual Studio Pro, if I go to Tools -> Extensions and Updates, NCrunch is listed under the "Installed" section.
Within Enterprise, NCrunch does not show in the Installed section. It is available in the "Online" (VS Marketplace) section, but at v3.8 only.

Is this an issue within NCrunch (maybe the installer), or with my system configuration maybe?
Remco
#2 Posted : Monday, June 12, 2017 2:14:51 AM(UTC)
Rank: NCrunch Developer

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

Thanks: 664 times
Was thanked: 781 time(s) in 743 post(s)
Hi,

This is a known problem and a limitation with the NCrunch installer. Building an MSI that can have multiple dynamically derived install paths is problematic. I haven't yet found an acceptable solution to this problem.

For now, it's best to just install the product manually if you have multiple versions of VS2017 installed side-by-side.
mcse3010
#3 Posted : Thursday, June 15, 2017 1:16:37 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 6/4/2017(UTC)
Posts: 3
Location: United States of America

I had the same problem, only I had VS 2017 Community and VS 2017 Pro installed... So we're all programmers here, what are you using to build your msi... WiX or InstallShield or NSIS or some other setup -- maybe one of us can help! :)

My solution was just to uninstall community (which I had intended to do anyway)... but how do you "install it manually"?
MendelMonteiro
#4 Posted : Thursday, June 15, 2017 3:25:02 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 8/20/2015(UTC)
Posts: 1
Location: France

Was thanked: 1 time(s) in 1 post(s)
1 user thanked MendelMonteiro for this useful post.
Remco on 6/15/2017(UTC)
Der-Albert.com
#5 Posted : Monday, June 19, 2017 9:27:50 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 5/17/2011(UTC)
Posts: 102

Was thanked: 16 time(s) in 14 post(s)
Maybe i overlook this in a other thread, why you are not using a vsix for the installation? This should solve these kind of problems.
Remco
#6 Posted : Monday, June 19, 2017 10:48:43 AM(UTC)
Rank: NCrunch Developer

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

Thanks: 664 times
Was thanked: 781 time(s) in 743 post(s)
VSIX have their own complications in terms of support and maintenance.

The VSIX format is different between versions of VS, so we'd need a whole different install strategy for each different VS version. I expect there will also be limitations that will create trade-offs.

These problems are probably not insurmountable but still have a price attached to them.
Der-Albert.com
#7 Posted : Tuesday, June 20, 2017 3:40:13 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 5/17/2011(UTC)
Posts: 102

Was thanked: 16 time(s) in 14 post(s)
I don't think that there are many problems with the VSIX Installer. Because the manual deployment is simply Copy & Paste, Unlocking Files, starting devenv. So nothing special. From that Side i can't imagine problems for that.

Now you are putting the unhandy work of manuell installation to every User with multple instances of Visual Studio 2017. Which may lead that some customer saying, this is annoying. No worth the effort, because i allready have Live Unittesting in my edition.

Think about first time users who would like test NCrunch. They install NCrunch, then start an instance of Visual Studio 2017... and nothing visible, no NCrunch ... oh, what a peace of sh*t ... uninstalling. you may have lost a new customer.

With the VS2017 VISX Format (older Version can still use the old MSI), so you have only support one extra format for the VS2017 lifetime. With VSIX you don't need an Install Strategy, do it like the vsix way.
Also you can even ngen the extgension assemblies, which may lead to performance improvements.
Der-Albert.com
#9 Posted : Tuesday, June 20, 2017 3:45:41 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 5/17/2011(UTC)
Posts: 102

Was thanked: 16 time(s) in 14 post(s)
Also to think about, there is a 3.10.2 Preview Version of NCrunch, which has a workaround for the multiple marker problem (have this allday). But i will not test this before the final release, because to much hassle to update.
Remco
#8 Posted : Tuesday, June 20, 2017 11:19:00 PM(UTC)
Rank: NCrunch Developer

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

Thanks: 664 times
Was thanked: 781 time(s) in 743 post(s)
Der-Albert.com;10667 wrote:
I don't think that there are many problems with the VSIX Installer. Because the manual deployment is simply Copy & Paste, Unlocking Files, starting devenv. So nothing special. From that Side i can't imagine problems for that.

Now you are putting the unhandy work of manuell installation to every User with multple instances of Visual Studio 2017. Which may lead that some customer saying, this is annoying. No worth the effort, because i allready have Live Unittesting in my edition.

Think about first time users who would like test NCrunch. They install NCrunch, then start an instance of Visual Studio 2017... and nothing visible, no NCrunch ... oh, what a peace of sh*t ... uninstalling. you may have lost a new customer.

With the VS2017 VISX Format (older Version can still use the old MSI), so you have only support one extra format for the VS2017 lifetime. With VSIX you don't need an Install Strategy, do it like the vsix way.
Also you can even ngen the extgension assemblies, which may lead to performance improvements.


Understood. Say rather that I am not disagreeing VSIX is a solution, more that the priority of this needs to be weighed relative to other things as in the broader context, work on even the simplest of installers always takes far longer than expected. It would probably make sense to track this in uservoice.
Der-Albert.com
#10 Posted : Wednesday, June 21, 2017 9:41:44 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 5/17/2011(UTC)
Posts: 102

Was thanked: 16 time(s) in 14 post(s)
1 user thanked Der-Albert.com for this useful post.
Remco on 6/21/2017(UTC)
Users browsing this topic
Guest (3)
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.056 seconds.