Open dhoehna opened 2 years ago
In Using the bootsrapper in a non-MSIX package the recommendation is to set WindowsPackageType to none.
WindowsPackageType
none
VS throws two cryptic errors
"Visual C++ 2015-2019 Runtime for Universal Windows Platform Apps v14.0" which targets platform "UAP"
Project "AppLifeCycleTest" targets platform "Windows", but references SDK "Visual C++ 2015-2019 UWP Desktop Runtime for native apps v14.0" which targets platform "UAP"
The solution to remove these errors is to Include <WinUISDKReferences>false</WinUISDKReferences> in the .*proj file.
<WinUISDKReferences>false</WinUISDKReferences>
.*proj
<WindowsPackageType>None</WindowsPackageType>
No errors.
No response
Visual Studio 2022
IDE: VS 2022 Enterprise Project: C++ Console application.
I didn't test this with a C# application, or different versions of Visual Studio.
Describe the bug
In Using the bootsrapper in a non-MSIX package the recommendation is to set
WindowsPackageType
tonone
.VS throws two cryptic errors
"Visual C++ 2015-2019 Runtime for Universal Windows Platform Apps v14.0" which targets platform "UAP"
Project "AppLifeCycleTest" targets platform "Windows", but references SDK "Visual C++ 2015-2019 UWP Desktop Runtime for native apps v14.0" which targets platform "UAP"
The solution to remove these errors is to Include
<WinUISDKReferences>false</WinUISDKReferences>
in the.*proj
file.Steps to reproduce the bug
<WindowsPackageType>None</WindowsPackageType>
to the project file.Expected behavior
No errors.
Screenshots
No response
NuGet package version
No response
Packaging type
No response
Windows version
No response
IDE
Visual Studio 2022
Additional context
No response