Search Issue Tracker
Active
Under Consideration for 2.0.X
Votes
0
Found in [Package]
2.0.20
Issue ID
VS-86
Regression
No
Error "The type or namespace name 'RuntimeInspectorNamespace' could not be found" when the package file path contains the "&" symbol
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/MainScripts/NewMonoBehaviourScript.cs” Script in Visual Studio
3. Observe Visual Studio Error List or Editor’s Console
Expected result: No Errors exist
Actual result: Error “The type or namespace name 'RuntimeInspectorNamespace' could not be found“ is present
Reproducible with: 2.0.22 (2022.3.61f1), 2.0.23 (2022.3.61f1, 6000.0.47f1, 6000.1.0b15, 6000.2.0a9)
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Notes:
- Package path contains "&" (ampersand) character in its file path
- Incorrect *.csproj with incorrect XML notation is generated (<Link>Runtime Inspector & Hierarchy\Plugins\RuntimeInspector\Scripts\RuntimeInspector\Fields\RectField.cs</Link>)
- "&" should be "&" in XML
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- Module installation fails with "Download failed: Validation Failed" errors when using beta.2 Hub version
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Shader Graph Category dropdown cannot be expanded/collapsed when clicking on the text
- Different text alignment in the column header in Entities "System" window
Add comment