Search Issue Tracker
Active
Votes
6
Found in [Package]
2018.4
2019.4
2019.4.16f1
2020.2
2021.1
2021.2
Issue ID
1300112
Regression
No
The csproj file for an asmdef targets .net Framework 4.7.1 when the Project is set to .net Standard 2.0
How to reproduce:
1. Create a new Unity project
2. Make sure Project Settings > Player> API Compatability Level is set to ".net Standard 2.0"
3. Create an asmdef file
4. Open the .csproj file generated by that asmdef in a text editor
5. Notice the <TargetFrameworkVersion>
Expected results: It is set to .Net Standard 2.0
Actual results: It is set to v4.7.1
Reproducible with: 2018.4.30f1, 2019.4.17f1, 2020.2.2f1, 2021.1.0b3, 2021.2.0a2
Comments (2)
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
- 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
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
NielsTerHeijden
Mar 01, 2023 14:49
I meant 2022.2
NielsTerHeijden
Mar 01, 2023 14:49
This is still a problem in 2020.2 where .Net Standard 2.1 is expected