Closed pygmypenguin closed 1 year ago
@pygmypenguin I don't think this issue has anything to do with WinGet. It appears to be an issue with Visual Studio.
You could try: https://developercommunity.visualstudio.com/VisualStudio/report
hm you're right, my apologies
No worries. I hope I pointed you in the right direction.
Brief description of your issue
I have a desktop application that currently builds and run with no issues. It is build primarily on WPF, with a couple older controls in WinForms and one vcxproj that enables directX rendering. This application currently builds and publishes with Visual Studio's msbuild.exe. In order to modernize our deployment, we want to add a Windows Application Packaging project to take advantage of some modern versioning and distribution principles.
After going through the "Add a new project wizard" to add this project, Visual Studio's built-in "build" command fails with
Specified EntryPointExe '' was not found in the project outputs
. I've seen a few different solutions online about how to "fix" this but none of them have worked, and all of them seem to require going into the .wapproj or Project.appxmanifest and modifying various elements manually. I would rather not do this if possible, since it appears that these two file types are not very well documented.Steps to reproduce
Ctrl + Shift + B
)msbuild -p:Configuration=Release -p:Platform=x64
)Expected behavior
The solution builds with no errors
Actual behavior
The solution fails to build with the following output:
Environment
wapproj (TesseractXL.MSIX.wapproj) relevant property groups: