-
Notifications
You must be signed in to change notification settings - Fork 305
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
Creating a singleExe from UnPackaged app breaks the latest WindowsApp SDK #4390
Comments
You can Exclude Files using: I did not test new version, Its mechanism may have changed
|
The resources.pri file (and all other native libraries) are actually embedded into the .exe file now and extracted to a temporary directory when you start the application. I checked your sample app to see why it does not work: -You need to set WindowsAppSdkSelfContained to true (see warning during build). |
Do the suggested actions fix the problem? |
Thanks for answering, No @bpulliam, Still exe not launched when I use above suggestion given by @lhak and @ghost1372 I have attached my project application and the command which I use to generate the single exe. Please go through and could you please check my problem and provide a solution for this? Note: I feel it is broken in latest update SDK. |
@sudharsan-narayanan i created a new project with a new class library and i can publish app as single file and exe can be run without any issues. |
Describe the bug
Currently using the latest SDK 1.5.240428000, it fails to generate the
resource.pri
when creating the SingleExe. I think, it is breaking the latest SDK behavior.If we use the SDK version 1.4.240211001, It creates the SingleExe properly with all dependency files.
It's replicate in the CustomControl library project also.
Steps to reproduce the bug
CustomControl.zip
SimpleApp.zip
dotnet publish SimpleApp.sln -c Release -p:Platform=x64 -p:PublishSingleFile=true --self-contained true -p:WindowsAppSDKSelfContained=true
Note: Exe will not launch in launch SDK.
Expected behavior
It should launch the exe properly as like windows SDK (1.4.240211001).
Screenshots
In Version
1.4.240211001
In Version
1.5.240428000
NuGet package version
Windows App SDK 1.5.3: 1.5.240428000
Packaging type
Unpackaged
Windows version
Windows 11 version 22H2 (22621, 2022 Update)
IDE
Visual Studio 2022
Additional context
No response
The text was updated successfully, but these errors were encountered: