Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
 All Forums
 Visual Assist
 Technical Support
 VS2017 and VCINSTALLDIR

You must be registered to post a reply.
Click here to register.

Screensize:
UserName:
Password:
Format: BoldItalicizeUnderlineStrikethrough Align leftCenterAlign right Insert horizontal ruleUpload and insert imageInsert hyperlinkInsert email addressInsert codeInsert quoted textInsert listInsert Emoji
   
Message:

Forum code is on.
Html is off.

 
Check to subscribe to this topic.
   

T O P I C    R E V I E W
AJTAYLOR Posted - Oct 26 2017 : 1:39:35 PM
Bit of a weird one this. Disable Visual Assist (Tools | Extensions and Updates) then go to Package Manager console and type:

echo $Env:VCINSTALLDIR

It shows no value whether a project is loaded or not.

Enable Visual Assist then load a project and try the command again and you get:

c:\program files (x86)\microsoft visual studio\2017\professional\common7\ide\vc\

On my system.

Now, on the face of it this isn't an issue but it's messing up Clang compilation due to it using the value of VCINSTALLDIR to determine the location of cl.exe when using /fallback mode.

I think the Clang code can be improved to handle this case better (will submit a pull request at some point) but wondering why this environment variable is seemingly being set by this plugin.

2   L A T E S T    R E P L I E S    (Newest First)
sean Posted - Dec 18 2017 : 7:26:40 PM
case=112001 was opened for this regression.
case=112001 is fixed in build 2248.
Jeff Posted - Oct 26 2017 : 6:14:34 PM
The setting of VCINSTALLDIR appears to be a result of a fix related to NuGet repositoryPath (case=105958) in build 2231.

If the problem is critical, revert to build 2223 while we investigate further.

https://www.wholetomato.com/features/whats-new.asp#2223

© 2023 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000