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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment