-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: Specified EntryPointExe '' was not found in the project outputs #27
Comments
I'm hitting this issue as well. I have a WPF project that multi-targets both .NET Framework and .NET 8. I'd like to WAP the .NET 8 target, but I haven't found a way to do this. It gets confused about the multi-targeted nature of the reference project. |
I found how to reproduce this issue.
It seems adding windows build version to TargetFramework is causing this error. Remove this "10.0.17763.0" make it build fine. Visual Studio version 17.9.0 |
I updated to visual studio 17.9.3 and this is not longer reproducible |
Error still in VS 2022, V 7.10.3, MAUI App, .NET 8 APP:
MSIX Setup Project: Error: |
When generating an msix for a project that uses the
<TargetFrameworks>
attribute instead of the<TargetFramework>
attribute this error is given. I guess the MSIX Packaging project template is not compatible with this newer attribute?My project was targeting net5.0-windows only but had previously also targetted net48. Once I found the cause it was easy to reproduce, and it also happens for projects that have this attribute and do use multi-targetting, so targetting net5.0-windows;net48 will not work either. You have to use the
<TargetFramework>
attribute instead.Is this by design, a choice or is this supposed to work with the
<TargetFrameworks>
attribute as well.The text was updated successfully, but these errors were encountered: