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
- Render Objects Renderer Feature are not writing to the Depth Buffer when Write Depth is enabled
- Field names under "Anchors" in the RectTransform Component don't get focused when "tabbing" through the fields
- Project Browser's Search by Type stops working after importing Assets into a Project and searching for Types "In Assets" with Search Engines Project Preference Settings set to Advanced
- The Particle System Trail module creates Trails with a lighter coloring than the particles when the Color Space is set to Linear
- Crash on "in __pthread_kill" when running the built application that has UNITY_EDITOR scripting symbol in conditional compilation
Add comment