Search Issue Tracker
Third Party Issue
Third Party Issue in 2.0.X
Votes
0
Found in [Package]
2.0.20
Issue ID
VS-89
Regression
Yes
Namespace references are not updated when a package is installed while Visual Studio is open
How to reproduce:
1. Create and open a new project
2. In the toolbar, navigate to Window > Package Management > Package Manager
3. In the Package Manager window, delete the “Timeline” package
4. Create and open a new C# script
5. Back in the Package Manager, install the “Timeline” package
6. In Visual Studio, enter “using UnityEngine.Timeline;”, at the top of the script
7. Observe the Error List in Visual Studio
Expected result: No errors are thrown
Actual result: CS0234 error is thrown
Reproducible with: 2.0.11 (6000.0.51f1, 6000.2.0b6), 2.0.23 (2022.3.63f1, 6000.0.51f1, 6000.1.8f1, 6000.2.0b6)
Not reproducible with: 2.0.9 (2022.1.0a1, 6000.0.51f1, 6000.2.0b6)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
- Full error: CS0234 “The type or namespace name 'Timeline' does not exist in the namespace 'UnityEngine' (are you missing an assembly reference?)”
- The error is only thrown in the IDE, no error is thrown in the Editor
- Restarting the IDE fixes the issue
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Group Selection title text size is smaller in renaming than the actual font size
- Rich Text is not correctly highlighted when searching through Debug Logs in the Console window
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
Resolution Note:
We have reported this issue to Microsoft they suggested to make sure Automatic Project Reloading is enabled in VS Options to avoid this problem
.SDK style projects will allow this to be supported natively in VS.
Resolution Note (2.0.X):
We have reported this issue to Microsoft they suggested to make sure Automatic Project Reloading is enabled in VS Options to avoid this problem
.SDK style projects will allow this to be supported natively in VS.