Search Issue Tracker
Fixed in 2020.1
Fixed in 2018.4, 2019.3
Votes
1
Found in
2017.4
2018.4
2019.3
2019.3.0f3
2020.1
2020.2
Issue ID
1208183
Regression
No
Only a small subset of Attribute declarations are included in UnityEngine.CoreModule.Jetbrains.Annotations namespace
How to reproduce:
1. Open existing or create a new project
2. Import the attached script "StatiClass.cs"
3. inspect Console window
Expected result: No errors in the Console window
Actual result: "The type or namespace name 'SourceTemplate' could not be found" error in the Console window
Reproducible with: 2017.4.37f1, 2018.4.18f1, 2019.3.4f1, 2020.1.0b1, 2020.2.0a2
Workaround: Add attribute declarations to one of the source files as per instructions at https://www.jetbrains.com/help/rider/Code_Analysis__Annotations_in_Source_Code.html#embedding-declarations-of-code-annotations-in-your-source-code
Note: List of annotation attributes supported by Rider is available at https://www.jetbrains.com/help/rider/Reference__Code_Annotation_Attributes.html
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
- Styling issues in the app toolbar
- Perforce integration - Attempting to add a P4Ignore ignored file does nothing
- URP ScriptableObject SerializeField value set to default during the first Import
- Variables use old overridden values on Prefabs when a variable has FormerlySerializedAs attribute
- [GPU PLM] 100% repro crash when baking EnterTheRoom with 4K maps when using system allocator
Resolution Note (fix version 2020.1):
Fixed in 2020.2.0a6. Built-in attributes for JetBrains Annotations have been modernized and include all new annotations (minus ASP/Razor attributes which have no relevance to Unity). For more info on these attributes, see https://www.jetbrains.com/help/resharper/Code_Analysis__Code_Annotations.html
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b9
Resolution Note (fix version 2019.3):
Fixed in 2019.3.14f1
Resolution Note (fix version 2018.4):
Fixed in 2018.4.24f1