Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
User name:
Password:
Save Password
Forgot your password?

 All Forums
 Visual Assist
 Technical Support
 Installer not seeing VS 2017
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

kberson
New Member

USA
2 Posts

Posted - Oct 05 2017 :  10:11:21 AM  Show Profile  Reply with Quote
I have both Visual Studio 2015 & 2017 but the installer is only seeing 2015, not 2017. Help!

feline
Whole Tomato Software

United Kingdom
18724 Posts

Posted - Oct 05 2017 :  1:13:33 PM  Show Profile  Reply with Quote
What is the full name of the installer? If you have an old installer, for a version of VA that was released before VS2017 was released, the installer won't support VS2017.

If you are trying to install VA 2237 and it is not picking up VS2017, which version of VS2017 are you using?

zen is the art of being at one with the two'ness
Go to Top of Page

kberson
New Member

USA
2 Posts

Posted - Oct 05 2017 :  6:45:14 PM  Show Profile  Reply with Quote
Yep, that's what it was. I ran an update install VS2017, and now Visual Assist is seeing it. Thanks!

Edited by - kberson on Oct 06 2017 09:36:18 AM
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
18724 Posts

Posted - Oct 06 2017 :  06:27:57 AM  Show Profile  Reply with Quote
Thank you for the update, I am glad this is now working well for you

zen is the art of being at one with the two'ness
Go to Top of Page

.oisyn
Tomato Guru

162 Posts

Posted - Oct 09 2017 :  5:51:22 PM  Show Profile  Reply with Quote
I'm seeing the same issue. I'm trying to install 2237 (VA_X_Setup2237_0.exe), and I'm using VS 2017 Community 15.3.5.

The installer sees 2015, but the option for 2017 is grayed out and I cannot select it.


I was able to install VA through the VS extensions manager, but that installs an older version (2231)
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
18724 Posts

Posted - Oct 10 2017 :  09:19:43 AM  Show Profile  Reply with Quote
Have you previously installed VA on this machine for VS2017? I am wondering if this is a new install or an upgrade where you are seeing this problem.

What OS are you using?

What is the name of the installer you are running? I am wondering if you are trying to install the latest version of VA, or an older version.

Is the machine where you are seeing this problem connected to the internet, and fully up to date?

zen is the art of being at one with the two'ness
Go to Top of Page

.oisyn
Tomato Guru

162 Posts

Posted - Oct 11 2017 :  04:54:48 AM  Show Profile  Reply with Quote
I had a year-old version of VA installed, together with VS 2015 Community. I recently installed VS 2017 Community using the web installer, so it was 15.3.5 from the start. Then I downloaded the latest Visual Assist (VA_X_Setup2237_0.exe), and it only saw VS 2015.

Interestingly enough, on my PC at work I installed VS 2017 Professional yesterday, and the same installer of VA did see VS 2017 in that case. The steps have been roughly the same - at work I also had a year-old version of VA together with VS 2015. The only difference is that I installed the Professional version of VS 2017, rather than Community.

I'm using an up to date Windows 10 (64 bits), and it is connected to the internet.
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
18724 Posts

Posted - Oct 11 2017 :  08:31:44 AM  Show Profile  Reply with Quote
On the machine where you are having this problem, do you have the directory:

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

if so, which directories does it contain? I would normally expect you to see just:

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

but something is different somewhere. Assuming you only have the Community directory, do you have the files:

C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VSIXInstaller.exe
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\devenv.exe

and are the files and directory readable by the current user, the user account you were using when you ran the VA exe installer?

zen is the art of being at one with the two'ness

Edited by - feline on Oct 11 2017 08:32:04 AM
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
18724 Posts

Posted - Oct 17 2017 :  10:41:06 AM  Show Profile  Reply with Quote
As a test, I have tried installing VS2017 into a custom install directory. I started with a Windows 7 machine with no IDE's at all installed, and then installed VS2017 Professional to the directory:

C:\Program Files (x86)\VS15
giving me:

C:\Program Files (x86)\VS15\Common7\IDE\devenv.exe

When I then run the VA 2237 exe installer, VA is aware that VS2017 is installed, and installs for this IDE perfectly happily. So it doesn't look like the install path to the IDE is a factor here.

Since this was a new install, VS2017 installed with version 15.4.0, in case that is a factor.

zen is the art of being at one with the two'ness
Go to Top of Page

.oisyn
Tomato Guru

162 Posts

Posted - Oct 19 2017 :  7:13:34 PM  Show Profile  Reply with Quote
Sorry for the late follow up. I've checked, and it is installed to the default directory (C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\devenv.exe)
Go to Top of Page

.oisyn
Tomato Guru

162 Posts

Posted - Oct 19 2017 :  7:26:19 PM  Show Profile  Reply with Quote
Well, I've updated to 15.4.1 and now the installer *did* see Visual Studio 2017 :)
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
18724 Posts

Posted - Oct 20 2017 :  07:51:51 AM  Show Profile  Reply with Quote
Thank you for the update, I am glad this is now working for you again. I am concerned at how the installer stopped seeing VS2017 and then started seeing it again though, especially since so far I have not been able to reproduce this on any of my machines.

If this happens again, can you please look in the %TEMP% directory for any "VSIXInstaller_*.log" files, if we are lucky these might offer a clue as to what is happening here.

Also, what is the full path to your "devenv.exe", and the version of VS2017 you are using, just in case your community edition is installed to a path with a different name.

zen is the art of being at one with the two'ness
Go to Top of Page

.oisyn
Tomato Guru

162 Posts

Posted - Oct 20 2017 :  7:39:06 PM  Show Profile  Reply with Quote
I mentioned that in a previous post, it's C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\devenv.exe
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
18724 Posts

Posted - Oct 21 2017 :  07:21:31 AM  Show Profile  Reply with Quote
Thank you, yes, I know you did, but I was thinking about future posts about the same problem. Apologies for not making that clear.

We have seen a similar problem come up, but only when the version of VS2017 changed, for example, using the Ultimate version during the beta period, but then moving to the Professional release version, so the install directory name and version are no longer in sync. However that isn't what happened here, so still no good theory as to what went wrong.

zen is the art of being at one with the two'ness
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
© 2023 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000