Search Issue Tracker
Not Reproducible
Votes
0
Found in [Package]
2.0.1
Issue ID
VS-23
Regression
Yes
[Visual Studio Editor] Scripts opened in a newly created project are not referenced to the project
How to reproduce:
1. Create a new project
2. Create a new C# script in the Project window
3. Open the script with Visual Studio
4. Observe the script
Expected result: Solution Explorer shows up, script referenced to the project
Actual result: Solution Explorer doesn't show up, script not referenced to the project
Reproducible with: 2.0.1 (2020.1.0b7, 2020.1.0b10, 2020.2.0a12)
Not reproducible with: 2.0.0 (2020.1.0b6)
Could not test with: 2017.4.40f1, 2018.4.23f1, 2019.3.15f1 (Visual Studio Editor package not available)
Note: After making some changes in the script and then re-opening it, the script gets referenced to the project and Solution Explorer shows up. In 2020.1.0b7 the very first created script is losing reference to the project and the second created script will be referenced correctly. In 2020.1.0b6 updating the Visual Studio Editor and then creating new scripts will result in all of the scripts losing reference to the 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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Resolution Note:
Unable to reproduce in the versions stated.