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.
-
shubhamswaraj2021
Aug 18, 2020 05:00
good one <a href="https://www.lyricsauto.com">lyricsauto</a>
-
akkip6526
May 20, 2019 11:23
Here you can play the mind blowing games are this website .http://myspades.org this is the perfect time pass you have enjoy the any time and more user are play the more games.
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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
This is a duplicate of issue #1037161