Search Issue Tracker
Fixed in 1.2.2
Votes
1
Found in [Package]
2019.2.0a9
2019.3
2019.3.15f1
2019.4
2020.1
2020.2
Issue ID
1253188
Regression
Yes
[VS Code] .sln file isn't updated when Scripts are imported and Visual Studio Code is used as the External Script Editor
How to reproduce:
1. Create and open a new project
2. Right-click in the project window and select Import Package > Custom Package
3. Import the attached "TestScripts.unitypackage" package
4. Open the "Class2" Script from the "Test" folder
5. Right-click on the "Class1" name
6. Select "go to definition"
Expected result: "Class1.cs" file is opened and the Class definition is shown
Actual result: "No definition found for 'Class1' error pops up
Reproducible with: 2019.2.0a9, 2019.2.0a14, 2019.3.16f1, 2019.4.0f1, 2020.1.0b11, 2020.2.0a14
Not reproducible with: 2018.4.23f1, 2019.2.0a8, 2019.2.0b1, 2019.2.21f1
Notes:
-This also reproduces with local Packages and Scripts pasted directly into the Assets folder
-The associated .sln file doesn't contain "Class1.cs" and "Class2.cs" files until the project files are regenerated
-This doesn't reproduce if Rider or Visual Studio are selected as External Script Editors
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
- Process deadlocking waiting on lock
- Animation clip does not play when reimporting an FBX file with changes to some of the Import Settings
- TMP emojis are rendered incorrectly and appear excessively pixelated when the Font Size is reduced
- Crash on YAMLWrite::OutputToCachedWriter when generating lighting
- Misaligned original Release Date lines in Release Tab of an Assets in Package Manager
Resolution Note (fix version 1.2.2):
Fixed in Visual Studio Code Editor 1.2.2