Step 3 - Convert Package from EXE to MSIX Download MSIX Packaging Tool We already have a signed EXE package built, signed, and available on our Code Snippets Manager GitHub repository that we can convert. When we reached out to the Electron community, the suggestions were to build our app as an AppX package and if needed convert it to an MSIX package using MSIX Packaging Tool. The other option, that Microsoft offers, is an MSIX package. We attempted to build an MSI package (which does not require reporting the installer scenario codes above) but encountered issues within our pipeline which we didn't want to adjust for a different build. Our CI/CD pipeline will build, package and sign an exe package for us, so why didn't we stay with this option? Because once you've chosen the exe option, Microsoft will ask for specific error codes for different installer scenarios, yet we couldn't find any information online supporting this. If you've followed our Sign and Notarize an Electron App post, this might seem like the easiest option. When you go to create a new product, there are two options you can choose from.īefore choosing one and filling out all of the information, please continue reading to ensure you make the right choice. After setting up your account in your dashboard home, you should notice an "App and games" workspace. To release an app on the Microsoft Store, you'll first need to sign up for a Microsoft Developer account. Step 1 - Create a Microsoft Developer Account
Follow the steps to have your app on the Microsoft Store in no time. You've finished coding up an app with Electron and now you want to release it to the Microsoft Store? Well, we've gone through the trial and error, so you don't have to.
0 kommentar(er)
