Search Issue Tracker
Won't Fix
Won't Fix in 2.0.X
Votes
0
Found in [Package]
2.0.11
Issue ID
VS-80
Regression
No
Autocomplete in Visual Studio breaks when an Assembly Definition name contains apostrophes
How to reproduce:
1. Open the attached project "Assembly Definition Unity Bug Project.zip"
2. Open Assets/NoAutocomplete.cs
Expected results: "using UnityEngine" is not greyed out and "MonoBehaviour" is not white
Actual results: "using UnityEngine" is greyed out and "MonoBehaviour" is white
Reproducible with: 2021.3.45f1, 2022.3.51f1, 6000.0.24f1, 6000.1.0a1
Reproducible on: Windows 10 22H2
Not reproducible on: No other environment tested
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note:
it works fine on a recent VS 2022 (tested with VS 2022 17.12.4) there are no plans to backport this
Resolution Note (2.0.X):
it works fine on a recent VS 2022 (tested with VS 2022 17.12.4) there are no plans to backport this