Your obligation is to me, not to Bill Gates. I may be (although I'll bet you I'm not) speaking entirely for myself here, but frankly I could not care less what Microsoft wants: my contract is with Serif, and I want - I've paid you for - a solution that works for me, not for Microsoft. Having said all this, I have paid for the whole lot as it is a staggeringly good offer. But we do it because it’s what customers want. My guess is that this is more to do with the fact that developing Windows Installer installations is a pain, and nobody wants to do it. Surely what matters is that MSI files can be signed. MSIX does (this means any MSIX that appears to be from Serif, will be guaranteed to be from us and only us).” “MSI does not require a digital signature. It can be uninstalled by deleting the folder or via the uninstall. Our install is registry-free and installs into a single directory. “MSI cannot guarantee that an uninstall will leave your machine in the exact state prior to install.”Īgain, it depends on how your application works. Windows Installer supports deltas, or did I misunderstand? See “Delta Patch” in the Microsoft documentation. “MSIX can perform in-app delta updates which are smaller and faster.” It can be done if you keep dependencies local. We’ve successfully sandboxed our EXE / DLL / MSI desktop application. You do not need to use MSIX to sandbox an application. “MSI apps are not sandboxed from other applications.” Our MSI installer does not require admin privileges, providing it’s installed into a directory that doesn’t require admin rights for write access. Whether admin privileges are required or not depends on what the installer does. “MSI requires admin privileges to install.” We are not flooded with “it doesn’t install” support calls. Sure, it fails sometimes, but it’s probably less than the 0.1% claimed for MSIX. “MSI had an installation success rate of ~85% (and we have many requests to our tech support team for v1 install failures). As a professional in the software industry responsible for a large, complex Windows application, I’ll give you my view on the most of the reasons. Oh I just read the reasons for the switch. Or has the new designed 'App' hit the wall so that this is no longer possible? It would be really sad if this is technically not possible anymore. And the struggle with Powershell scripts says to me: This makes more problem than it solves.īut the really big question is: Why do you not make a two way solution? Why dont make a regular Setup like V1? Firefox for example can do this also -> Exe Setup or MSI. So they are kicked out.Īs nice as it may be, it just isn't. So Windows 8(.1) is completly kicked out.Īnd the next big thing - Some companies don't want the Windows Store nor the App Installer per policies. And no, the 'Move' function in the Settings is not an alternative! If we move the content do D:\ for example we have struggle with the Trusted Installer in D:\ -> This is completely a mess up.Īdditionally MSIX is supported from Windon or later. ![]() (Yes ok, this is good for Code Integrity by the way) So we don't have really the choice for the location. The new MSIX has his own closed Folder in the `C:\ProgramFiles\WindowsApps\` this is protected by the TrustedInstaller. Windows Installer is an old one that has superseded by the new MSIX.īut there are some disadvantages about the managed Windows Installer. ![]() ![]() I can understand why MSI is not an option.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |