Search Issue Tracker
Fixed in 2017.3.0f3
Votes
0
Found in
2017.3.0a3
Issue ID
940269
Regression
Yes
Individual installers unnecessarily detect and show a warning about Visual Studio 2017 running
Steps to reproduce:
1. Create a new Unity Project
2. Create a new script and open it in Visual Studio 2017
3. Go back to he Editor and open Build settings
4. Download an installer for a Build target(e.g. WebGL)
5. Run the installer
Expected result: the installer warns the user about Unity versions running
Actual result: installer also warns the user that Visual Studio is running, which should only happen if you want to install VS along with the main Downloads Assistant
Reproduced on 5.6.0f2, 5.6.3f1, 2017.1.0p3, 2017.2.0b6, 2017.1.0a3 individual installers(Build targets or Editor installers)
Not reprodudeced with 5.5.4p2, 5.6.0b1 or regular Download Assistant across any versions
Verified FIXED 2017.3.0a6
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment