Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.2f2
Issue ID
1032729
Regression
No
Unity project is not compatible with Visual Studio 2015 after IDE switch
How to reproduce:
1. Open user-submitted project (New Unity Project (3).zip)
2. Switch IDE setting from Visual Studio 2017 to Visual Studio 2015 (set in Edit->Preferences ...->External Tools; If IDE is already set to 2015 switch to 2017 again)
3. Open "NewBehaviourScript.cs"
Expected result: Unity C# project opens without issues
Actual result: Unity C# project won't load and the file opens without any project context.
Reproducible with: 5.6.6f2, 2017.1.3p4, 2017.2.2p3, 2017.3.2f1, 2017.4.2f2, 2018.1.0f2, 2018.2.0b3
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- Package Manager Filters (Status) dropdown is different color than Packages, Sort or Add package dropdowns
Resolution Note:
This is an issue with Visual Studio / Visual Studio Tools for Unity (VSTU). The bug report was sent to Microsoft.