How to produce single exe file after push for unpackaged app ? #2755
-
|
I used windows app sdk version 1.1.2 With these push settings: And what i get with
|
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 6 replies
-
|
Single exe file is not working dont use it |
Beta Was this translation helpful? Give feedback.
-
|
For me its working. |
Beta Was this translation helpful? Give feedback.
-
Put a InfoBar element |
Beta Was this translation helpful? Give feedback.
-
It's a redistributable. Unpackaged apps need to (successfully) call
It could be provided as a static library but that brings a ton of complications to the table starting with "Assumes you're using the same compiler version and settings" e.g. no help C# considering it's not implemented in C#. Or Rust. Or... It could be provided as source code but it's non-trivial and again assumes you're using C++... I thought there was more to make 'single file' work than this. @mikebattista ? |
Beta Was this translation helpful? Give feedback.
-
|
But what about Microsoft.WindowsAppRuntime.Bootstrap.dll save it somewhere in a known place along with installing the win app runtime, but why isn't it done this way? And after all, Microsoft.WindowsAppRuntime.Bootstrap.dll it seems to depend on the win app runtime so that there is some sense to download it together with the runtime. |
Beta Was this translation helpful? Give feedback.
-
|
You will need to include Honestly this whole WindowsAppSdk thing is not production ready. Even the beta tag would be a bold statement. The quality bar for the release version is exceptionally low for a microsoft product. WPF had its quirks when it first came out, but this whole stack is extremely frustrating to work with. The debugging experience in C# turns out to be a nightmare when you leave your hello world program. Every new version includes new regressions and bugs to basic functionality. Bugs like drag and drop crashing the app are there through numerous releases. Bugs like scrolling a listview crashing the app show that there is no testing in place even for the most elementary functions of the controls. This all has been mentioned and discussed in numerous community calls in which they always promise to do better. Nothing groundbreaking has happened so far. The microsoft-ui-xaml and this repository keep racking up issues in the thousands. I can't believe that the best strategy in 2022, if you want to develop a windows app, with a nice GUI, is to stick to plain old windows forms and look for controls from a professional vendor like DevExpress, etc. You get designer support (yes WinUI3 is lacking a real graphical designer), a proper debugging experience (did i mention the WinUI3 debugging experience is complete crap) and with all this tried and tested tools that just work. P.S.: I am mad and im venting here 😡 |
Beta Was this translation helpful? Give feedback.
-
|
I totally feel you ^^ I stick to boring Winforms, just because it works and is easy to publish smaller weekend projects. With that WinUI stuff, you have more trouble with getting it to work in first place than with the actual functionality of your program |
Beta Was this translation helpful? Give feedback.
-
Sooo true. Sad to say so :( |
Beta Was this translation helpful? Give feedback.
-
|
It´s May 2023 and i still would sign what @Balkoth said above. That whole beast is just a nightmare of its own. Even from a C# perspective. I don´t wanna even start talking about the C++ quirks i stepped over, when tested the whole stuff, for more than 40 hours. But the most disappointing aspect to me was the output size. Coming from 144 MB sized single EXE files (self-contained WinForms/WPF applications), i decided to check the size of a WinUI3 Hello-World app. Which ended up with a 119 MB EXE + 2 external files, which not really can be compiled into the EXE (see above posts). So, for C# there is still the framework-dependent way. Doing this in C# and WinForms/WPF is just a walk in the park. Everything works out of the box, without any quirks. Create your 145 KB framework-dependent WinForms/WPF EXE, make sure your clients have .NET 6 (or .NET 5, or .NET 7, or whatever) installed and you will sleep like a baby. Do the same thing with Windows App SDK and WinUI3 and see what happens... 😉 Besides the size, what i experienced working with Windows App SDK and WinUI3 for 40-50 hours in May 2023, was all in all one of the most horrible experiences i had in the last 10 years, when it comes down to Desktop UI development. At its best i would consider this a late beta. On good days. Not what i normally expect to see from MS. Sad to say. 😞 |
Beta Was this translation helpful? Give feedback.
-
|
Hi I'm working on fluent UI for wpf, maybe you'll like it. |
Beta Was this translation helpful? Give feedback.
You will need to include
<IncludeNativeLibrariesForSelfExtract>true</IncludeNativeLibrariesForSelfExtract>but resources.pri will still be separate.Honestly this whole WindowsAppSdk thing is not production ready. Even the beta tag would be a bold statement. The quality bar for the release version is exceptionally low for a microsoft product. WPF had its quirks when it first came out, but this whole stack is extremely frustrating to work with.
The debugging experience in C# turns out to be a nightmare when you leave your hello world program.
Every new version includes new regressions and bugs to basic functionality. Bugs like drag and drop crashing the app are there through numerous relea…