Search Issue Tracker
Duplicate
Votes
0
Found in
2018.2.0b6
Issue ID
1043329
Regression
No
VS Code doesn't generate a solution
Having a particular combination of packages makes Visual Studio Code not open the project solution properly.
Repro steps:
-download this manifest.json
-create a new project with Unity 2018.2 0b6
-go to the project folder-> Packages and replace the manifest.json with this one
-load up the project. Unity will take a bit to import all these packages
-ensure the Visual Studio code is your main code editor
-make a new script and try to open it
1 of 2 things might happen (i've had it happen a bit randomly of all the times i tried to repro this bug):
- Visual studio will just open that 1 file and 2 other files, but it won't recognise the project
- VS will open 2 instances: 1 will be that project and 1 will be the broken version of that project.
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
- “Label” name in Sprite Library Editor window lacks character limit causing long names go under the Object Field
- Preview image (screenshot) is not available after capturing snapshot in Memory Profiler
- Crash on UNITY_FT_Stream_ReadAt when changing TMPro properties after unloading an AssetBundle
- Particles spawn at the same position when using raw byte address buffer in VFX Graph
- Decal Shader Graph - Custom vertex interpolators are always 0
This is a duplicate of issue #1037161