Version 2.0 Additional Features

[YehudaKremer]

Hello,
i am writing here a list of features for version 2,
you welcome to add ideas and participate in improving this plugin 🛩️.

Version 2.0 Additional Features Planning:

• allow all configuration in the yaml file also as command line arguments (do it with one List<String> of fields names) - 👍8cdaef6
• expose all the options for the Signtool cli as msix configuration (Sign Tool documentation) - 👍faeb0f8
• expose all the options for the MakeAppx cli as msix configuration (MakeAppx documentation) - 🚫 no significant cli additions
• ui: progress bar status when runing - 👍4e74a8c
• shorten the long documentation - 👍b7cd530
• Handle Protocol Activation and Redirection Version 2.0 Additional Features #37 (comment) - 👍341f30b

[del-sec]

I'm not sure if this isn't already covered by the first point, but the ability to add extensions (like here) would be very useful.

[YehudaKremer]

I'm not sure if this isn't already covered by the first point, but the ability to add extensions (like here) would be very useful.

@del-sec very cool Feature, added here: 341f30b
thank you!

[YehudaKremer]

All Done 🎉
msix 2.0.0 is now available on pub.dev

[richard457]

@YehudaKremer Thanks for this awesome plugin, for a beginner in windows app and certification, would be nice to have a step-by-step on how to get the app signed and published to the windows store this can help a lot.

[richard457]

Found this If you publish your msix to Windows Store you dont need to sign it, Windows Store does it for you. To generate msix file for Windows Store use the --store flag or add store: true in msix configuration sction in your pubspec.yaml. in documentation but I am not sure if adding store: true is what is needed to just upload the app to app store i.e not need to add this # certificate_path: C:<PathToCertificate><MyCertificate.pfx>

certificate_password: 1234 (require if using .pfx certificate)