Search Issue Tracker
Fixed in 2.0.2
Votes
0
Found in [Package]
2020.1.0b6
2020.2.0a8
2020.2.0a13
Issue ID
1251157
Regression
Yes
[Scripting] Renaming the class name in the VisualStudio Code leads a new Script in the Unity Editor
Renaming the class name in the VisualStudio Code leads a new Script in the Unity Editor
Steps to Repro:
1. Create a new Project
2. Create a new Script in the Project > Assets > right-click > Create > C# Script
3. Open Script by double click on it to open in VS Code Editor
2. Change Script name to AAA in Unity Editor
3. Change Script's class name to AAA in VS and save and come back to Unity Editor
Expected Result:
Changes in Scripting is saved successfully
Actual Result:
One new Script is created
Reproducible on: 2020.2.0a13, 2020.2.0a8 , 2020.1.0b11, 2020.1.0b6
Working fine on: 2020.1.0a7, 2020.1.0b5, 2019.3.15f1, 2019.2.12f1, 2019.1.14f1, 2018.4.22f1, 2017.4.40f1
Environment: Windows 10 only
Workaround: Visual Studio Code Editor package downgraded to 1.1.4 works fine
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
- Celestial bodies order remains unchanged when the Distance setting is modified
- A memory leak occurs with massive terrain when camera position changes occur.
- No valid hits are returned when using RaycastCommand
- Camera is not overlooking the main Scene in Scene View in the HDRP Sample Template
- TextShadow properties are not applied when displayed in a custom MenuItem Window
Resolution Note (fix version 2.0.2):
Resolved by PR: https://ono.unity3d.com/unity/unity/pull-request/107392/_/2020.1/scripting/com.unity.ide.visualstudio