Search Issue Tracker
Fixed in 2017.3.0f3
Votes
0
Found in
2017.3.0a6
Issue ID
946419
Regression
Yes
[VS2017] After installing Visual Studio with Unity Download Assistant, future installers don't locate the installed VS
To reproduce:
0) Don't have VS2017
1) Run Unity Download Assistant
2) Install VS as one of the components
3) After installation finishes, run Unity Download Assistant (version doesn't matter)
Expected: Assistant runs without prompts
Actual: This is prompted right before anything http://i.imgur.com/37OiEvv.png
Note: Running VS once to make sure it works properly (and setting up license) doesn't help
Tested:
Installed VS with 2017.3.0a6, 2017.1.1f1, 5.6.3p2 assistant
After that ran these assistants (and installed all the corresponding Unities): 5.6.3p2, 2017.1.0f3, 2017.1.0p5, 2017.1.1f1, 2017.2.0b9, 2017.3.0a6
Tested on Microsoft Windows [Version 10.0.15063]
VS version that was installed: http://i.imgur.com/qYsbkZi.png
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment