baasfen.blogg.se - Msi software sucks

MSI SOFTWARE SUCKS .EXE
MSI SOFTWARE SUCKS INSTALL
MSI SOFTWARE SUCKS UPDATE
MSI SOFTWARE SUCKS WINDOWS

There could be special "winget-repackager"-as-a-Service tool set up by Microsoft (GitHub Actions/Cloud-based) where any.

MSIXBUNDLE packages, but provide re-packaging CI for. Alternatively the package manifest could include a transcribed, machine readable version number for winget to use internally such as "2.1.0-rc2" -> ".2" 3. NET System.Version so we could cover >96% of version numbers. They have required information fields, such as Publisher, ProductName, ProductVersion and a GUID for each package so while they permit a Version-String that may be hard to parse we could beef up winget-clis ability to parse "weirdo" non-numeric version strings such as "v10", "2.1.0-pre", "2.1.0-rc2", "3.0-alpha3" etc.

MSI SOFTWARE SUCKS WINDOWS

They have consistent silent arguments, they are registered by the Windows Installer database and as such can be queried programmatically. MSI packages aren't perfect, but they are a lot better than the wide variety of. This would provide the best possible user experience and communicate to OEMs, developers and partners the importance of MSIX. MSIXBUNDLE) application packages, because these are true "OS-manageable" packages in the sense one would expect from a package manager. Slim down the scope of winget-cli and the manifest format. Proposed technical implementation details (optional) There are no guarantees they can make to winget.

These programs, once installed, can be uninstalled, tampered with, moved, have their Uninstall-registry-key deleted by anything at any moment.

MSI SOFTWARE SUCKS .EXE

EXE installers are just dirty, supporting them will cause so many issues -> even now, in this super early beta, already there are tons of open issues on this GitHub that all just relate to something weird or unexpected in Nullsoft, Squirrel, InstallShield, FlexeraInstallAnywhere, INNO etc.

MSI SOFTWARE SUCKS INSTALL

EXE Setups may bundle and install dependencies such as MSVC++ Redists or Microsoft ODBC Driver that winget is unaware have been installed (dependency resolution is not possible and neither is keeping track of the patch levels of libraries or dependencies)

MSI SOFTWARE SUCKS UPDATE

Since the programs installed can update on their own and do not have a truly reliable way of fetching their version number - and even if they are not forced to have a version number that is comparable numerically (they might use a version string like "v10-0-pre-Build3002") winget cannot accurately keep track of them after the initial install.

EXE Setup installs per-user or per-machine

It is unclear to the user of winget whether an.

Even with silent arguments, some installers do not run/work when there is no user logged in or no graphical user session available (which breaks remote winget installs via ssh/WinRM when nobody is physically logged in to the machine).

Even with silent arguments, an installer may show a MessageBox on Error.

With silent arguments, some installers may choose undesirable defaults.Even with silent arguments, some installers invoke hidden windows that steal focus.There are no guarantees in install behavior and they all vary a lot:.They complicate the manifest format a lot with varying silent arguments and/or answer files.EXE Setups are often not "transactional" packages, aka changes they make are not reverted on uninstall Let us build the right thing now for the future, instead of reinventing the past we're tring to get away from so desperately What is wrong with supprting. Selection of glorified one-way install-scripts. I want to see how many others would preferĪ tiny starting software selection of REAL packages with all the goodies over a larger software Microsoft has MSIX, it's open-source,Īnd they have winget, it's open-source. This proposal is the formal version of replying "so what?" to this. Is not far enough along yet and it would significantly reduce the amount of available apps. Specifically continuing on this comment by replied there that the adoption of MSIX This is intended to be an open discussion about #223, Instead I propose a (more or less - see below) strict MSIX-only approach. This is a suggestion / spec / discussion on how I believe

Description of the new feature/enhancement