5 ms·
Just use WinUI 3. Opting into MSIX packaging no longer requires an App Container sandbox. More info here: https://learn.microsoft.com/en-us/windows/msix/deskto
by fassssst 2y ago
Just use WinUI 3. Opting into MSIX packaging no longer requires an App Container sandbox.
More info here:
https://learn.microsoft.com/en-us/windows/msix/desktop/desktop-to-uwp-behind-the-scenes https://learn.microsoft.com/en-us/windows/msix/desktop/deskt...
Full disclosure: I work at Microsoft.
- withinrafael 2y agorunFullTrust apps are still subject to file system and registry redirection as well as various capability checks. Running fully unencumbered requires restricted capabilities that only Microsoft can approve.
- mike_hearn 2y agoYou can opt out of those with manifest metadata. Capabilities aren't enforced if you distribute out of the app store.
- withinrafael 2y agoThe OS will enforce them at installation/launch time regardless of distribution method.
- mike_hearn 2y agoYes but what I mean is you can declare any capabilities you want, nothing prevents you just asking for whatever you need except Store review.
- jenscow 2y agoyou can turn some of that crap off: https://learn.microsoft.com/en-us/uwp/schemas/appxpackage/uapmanifestschema/element-virtualization-filesystemwritevirtualization https://learn.microsoft.com/en-us/uwp/schemas/appxpackage/ua...
- withinrafael 2y agoNote the warning on the page. > This element requires the unvirtualizedResources restricted capability. And if you click through the restricted capability link: > If your app declares any restricted capabilities, then you must provide info during the app submission process in order to be approved to publish your app to the Microsoft Store.
- jenscow 2y agoFor >1 minute incremental compile times? No thanks.
- eschaton 2y ago[flagged]
- userbinator 2y agoPerhaps the one you're replying to doesn't want a "truly large project".
- akira2501 2y agoThe complaint is that writing GUI apps is painful not that it's impossible. In particular, when compared to other platforms, windows has had 30 years, several frameworks, market dominance, and they all still end up getting a D- for one reason or another.
- utensil4778 2y agoYou're being an unnecessary dick. Long compile times are annoying and affect productivity. Some people are really sensitive to this type of disruption and it gets very difficult to stay in flow when the only thing you can do is sit and stare at a progress bar. This is particularly offensive to C# developers. Take your elitist attitude and your gigantic C++ monstrosity elsewhere. Tell me you haven't used a modern JIT language without telling me you're a scrub. Jesus.
- eschaton 2y agoAh, yes, I must be a C++ advocate who has never used a “modern JIT language.” I’ve actually been using them since before the term “JIT” was in common use, just like I used C++ before it had templates or exceptions. Incremental compile time on the order of a minute should not a big deal in a project. How would someone who can’t handle that have fared in our industry 30 years ago? Yes, faster compiles are nice, but they aren’t what will ultimately limit you unless you have an untreated medical condition.
- zerr 2y agoWhere's the GUI designer?
- pjmlp 2y agoWinUI 3 XAML C++ is a joke, versus the old C++/CX tooling in Visual Studio. Editing IDL files without any kind of Visual Studio tooling, manually merging generated C++ code, no designer.