Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2019.2.11f1
2020.1
Issue ID
1202873
Regression
No
[UWP] .targets and .vcxitems are imported in the wrong order in the generated .vcxproj file
How to reproduce:
1. Create a new project
2. Build the project for UWP
3. Navigate to the built project location
4. Open the .vcxproj file in a text editor
5. Inspect the import of "Microsoft.Cpp.targets" and "Unity Data.vcxitems"
Expected results: "UnityData.vcxitems" is imported first
Actual results: "Microsoft.cpp.targets" is imported first
Reproduced with: 2018.4.0f1, 2020.1.0a15
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
- The sidebar reopens when Unity Hub is started when Unity Hub was closed with the sidebar closed
- Characters are invisible in the TextField when certain Japanese characters are used
- "InvalidOperationException" is thrown when using Prefab > Replace to replace a Canvas GameObject with a Prefab that has an incompatible root Transform type
- Looping AudioSource resumes from the wrong playback position when the app is backgrounded and resumed on iOS Safari
- "AnyState Transition Created" action can be undone when pressing "Auto Generate Animation" on the uGUI GameObjects
Resolution Note (2020.1.X):
Swapping the two "Import" lines ("UnityData.vcxitems" and "Microsoft.Cpp.targets") breaks native plugins when building the generated VS project.
For some reason, when these imports are swapped, the native DLLs aren't copied from their source folders into the root output folder while building the project in Visual Studio causing an APPX error that breaks the build. This issue will require more investigative work to properly resolve, and doesn't meet our priority bar at this time.
Instead, the "swap" operation can be performed as a build post-process step in the Unity Editor using the PostProcessBuildAttribute (https://docs.unity3d.com/ScriptReference/Callbacks.PostProcessBuildAttribute.html).