Search Issue Tracker
Third Party Issue
Third Party Issue in 2.0.X
Votes
0
Found in [Package]
2.0.11
Issue ID
VS-64
Regression
No
Visual Studio Editor shows reference errors for unloaded incompatible DLL files
Reproduction steps:
1. Open the attached project "dll_bug.zip"
2. In Assets open script_example.cs script
3. Notice that there are no reference errors for the ConcurrentDictionary object
4. Add the attached System.Collections.Concurrent.dll to Assets
3. Click on the DLL file and disable all checkboxes in the Inspector
4. Open script_example.cs script again
Expected result: No reference error for the ConcurrentDictionary object is shown
Actual result: Duplicate reference error for ConcurrentDictionary object is shown even though the DLL file was unloaded and disabled for all platforms including Editor
Reproducible with: 2.0.12 (2019.4.37f1), 2.0.14 (2019.4.37f1, 2020.3.31f1, 2021.2.16f1, 2022.1.0b12, 2022.2.0a9)
Notes:
- Restarting the Unity or reimporting the script does not fix the error
- Does not reproduce with JetBrains Rider IDE
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
- Font character thickness does not adjust properly in UI Toolkit text when changing Bold Weight in Font Asset
- Multiple "[...] is inaccessible due to its protection level" errors are thrown when opening project with Unity Version Control installed
- Font character thickness does not adjust properly in UI Toolkit text when changing Bold Weight in Font Asset
- Sorting icons are tiny and misaligned in Import Activity window
- The Undo system does not record HideFlags.HideInHierarchy changes
Resolution Note:
Our apologize for the late response to this issue. The issue is not the the Visual Studio Tools integration but because of a package that is duplicating DLLs. The packages/codes responsible for such duplicate should address this on their side. Thank you.
Resolution Note (2.0.X):
Our apologize for the late response to this issue. The issue is not the the Visual Studio Tools integration but because of a package that is duplicating DLLs. The packages/codes responsible for such duplicate should address this on their side. Thank you.