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
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
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