Provide an .MSIX installation package.

[RokeJulianLockhart]

My rationale is available at felixrieseberg/windows95#221 (comment).

[github-actions]

Consider supporting the developer on Patreon to increase priority of all your issues, get access to private discord and other rewards.
Patreon page: https://www.patreon.com/sigma_file_manager

[aleksey-hoffman]

You can install the app with winget install sigma
I will publish v1.5 update today. I think, it will need a few days to update in the winget system

[aleksey-hoffman]

I'm not sure what you mean by "allow proper management".
Please feel free to re-open the issue if it's still relevant

[RokeJulianLockhart]

#169 (comment)

@aleksey-hoffman, while winget functions as a package manager, it differs from other package managers in that it doesn't enforce a standardized package format. This can make managing software installed through winget difficult without a standardized package format too.

As aforementioned, felixrieseberg/windows95#221 (comment) provides some additional rationale.

[aleksey-hoffman]

I can build a MSIX package, but it will be unsigned
Do you know if unsigned build is suitable for winget?

[RokeJulianLockhart]

#169 (comment)

@aleksey-hoffman, please remember that winget is merely the package manager, and, like most (except https://github.com/canonical/snapcraft, I suppose) supports repositories. I do not believe that WinGet itself prevents installation of unsigned packages. I believe that the default msstore repository mandates that all packages be signed, but that shouldn't affect the winget repository. I suggest that you submit an issue at https://github.com/microsoft/winget-pkgs/issues/new?assignees=&labels=Help-Wanted%2CPackage-Request&template=package_request.yml&title=%5BPackage+Request%5D%3A+ about this.

[aleksey-hoffman]

I don't fully understand the issue, mate.
It's already available on winget and it seems it works as intended.

What would the MSIX file change?

[RokeJulianLockhart]

#169 (comment)

@aleksey-hoffman, I believe that to explain it any more I risk unnecessarily duplicating what the relevant official MSIX documentation already explains better than I am able to, so I suggest that you read it. If you understand how your current installer operates, you should very quickly be able to ascertain how native manipulation via PowerShell and uninstallation without any remains are desirable.

Any technical support is probably best received by creating a pull-request at the relevant WinGet manifest that replaces the current installer's URI with a new one for the MSIX package. The moderators shall assist you with any problems relevant to the packaging at there. I'm happy to create an issue to replace it, but can't without a package already produced.

[RokeJulianLockhart]

#169 (comment)

@aleksey-hoffman, about the package signature, I've asked microsoft/winget-pkgs#157365 (comment), and I recommend that you follow microsoft/msix-packaging#332 (comment). I can imagine how annoying that requirement is.

[aleksey-hoffman]

Cheers mate
They probably won't make it any simpler though