Search Issue Tracker
Fixed in 2022.1.X
Duplicate in 2020.3.X
Votes
2
Found in
2018.4
2019.4
2020.3
2020.3.6f1
2021.1
2021.2
Issue ID
1334636
Regression
No
[UWP] Not adding NET_STANDARD_2_0 define
How to reproduce:
1. Open the attached "New Unity Project.zip" project
2. Switch to UWP
3. Select .NET Standard 2.0 Scripting backend in Player settings
4. In Project window select Packages > Microsoft.Extensions.DependencyInjection > Microsoft.Extensions.DependencyInjection.dll
5. See define constraints in Inspector window showing "define constraint is incompatible" error
6. Open "Assembly-CSharp.csproj" file with a text editor
7. Search for .NET version in DefineConstants line
Expected result: "NET_STANDARD_2_0" constraint is present
Actual result: "NET_4_6" constraint is present
Reproducible with: 2018.4.35f1, 2019.4.27f1, 2020.3.9f1, 2021.1.8f1, 2021.2.0a17
Notes:
- Not reproducible on Standalone
Comments (1)
-
holo-krzysztof
Apr 04, 2022 09:58
Can you please backport this to 2020.3.X? Switching to newer version is not even close to being viable for XR projects.
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
- Points Lights are getting culled prematurely when using Forward+ and Deferred+ rendering paths
- Search's Indexing settings in the Preferences window are not searchable
- Crash on block_locate_free when opening a specific project
- "Project connected" pop opens again after closing it
- Cloud Code Authoring logs "JsAssetHandler:OpenAsset (int,int) does not match any of [OnOpenAssetAttribute] expected signatures" when opening or switching scenes and having the Deployment Package Installed
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a2