Search Issue Tracker
Fixed in 2.0.2
Votes
0
Found in [Package]
2020.1.0b6
2020.2.0a8
2020.2.0a13
Issue ID
1251160
Regression
Yes
[Scripting] Deleted Script from Unity Editor is available in the Visual Studio Code Editor
Deleted Script from Unity Editor is available in the Visual Studio Editor. When Script is edited and save it appears in the Unity Editor
Steps to Repro:
1. Create a new Project
2. Create a new Script
3. Open it in the Visual Studio Code Editor
4. Delete the Script from the Unity
Expected Result:
Script disappeared from the Visual Studio Code
Actual Result:
Script is still available in the Visual Studio and can be edited and after saving it appears in the unity editor
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 downgrade 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
- Create Node Menu is not closing and “NullReferenceException: Object reference not set to an instance of an object” error is thrown when Shader Graph window is closed
- Assert error is thrown when the Editor language is set to one of the experimental ones in an HDRP project
- A BatchDrawCommand is using a pass from the shader “Universal Render Pipeline/Particles/Lit” that is not SRP Batcher compatible
- The Scene does not get rendered in the Player when MSAA is enabled and more than one Camera is used
- Crash on mono_object_get_class when generating Font Atlas of a specific font file
Resolution Note (fix version 2.0.2):
Resolved by PR: https://ono.unity3d.com/unity/unity/pull-request/107020/_/scripting/com.unity.ide.visualstudio