We think this is a great approach that takes the manual steps out of store publishing and encourages developers to keep their apps up to date in the store. This GitHub action, available in the GitHub Marketplace, automates the build and packaging process, and then updates the store listing with the new package, all triggered as part of your CI/CD pipeline. We also have Continuous Integration / Continuous Delivery (CI/CD) support from GitHub, built upon these same store APIs. This API is useful if your account manages many apps, and you want to automate and optimize the submission process for these assets. However, for a more automated approach, you can use our REST APIs for store submission and update.Īfter your initial submission of your app, you can use the Microsoft Store submission API for your Win32 app to programmatically query and create new submissions for the app. It’s easy to submit updates to your app right through the Partner Center UI. You can provide these custom return codes when submitting your installer to the store. To provide the best customer experience when using an EXE installer (like setup.exe), the Store supports suitable customer facing messages and actions for the return codes during setup. The store handles standard MSI return codes automatically. As long as your app and installer comply with store requirements and policies, there’s no need to change anything to gain the discoverability, analytics, and other benefits from listing in the store. That installer is served up from your own versioned URL and installs your app. We use your installer, in silent mode, without modification. We designed the Win32 store support to be as easy as possible for application developers with existing apps to take advantage of. When you use your own commerce system for your non-gaming apps, you keep 100% of the revenue (subject to the terms of your own commerce system provider and payment processor), and do not pay Microsoft anything for publishing or selling your app. To support your apps without changes, we’re enabling you to bring your own commerce system for in-app purchases. The new Microsoft Store on Windows supports Windows 11 alongside Windows 10, reaching more Windows customers than ever.
At Build 2022, we’ve announced that the preview program was successful, and we’ve opened up Win32 app publishing to everyone!īringing your Win32 app to the Microsoft Store adds another distribution channel for your traditional desktop app by making it discoverable to Windows customers right within Windows, all while keeping your existing build production workflows. NET (WPF, Windows Forms, console) to C++, WinUI, MFC, Qt, Flutter, OpenGL, Pascal, Java, Electron, and so much more, to be part of the Windows Store catalog. MSI installers, and built using anything from. In recognition of that, last year, we introduced a preview program to enable those traditional desktop apps, commonly called “Win32” apps, packaged in. It can also be a lot of work for smaller developer teams to gain the right insights into the deployment and use of their applications and to get the right discoverability for their apps. Those apps are distributed all around the web, making it challenging for a customer to know if an app is reputable or not. MSIX installers, complete with app identity and a focus on both safety and simple install experience.īut the utility and desirability of the Windows platform comes largely from the huge selection of powerful and productive traditional desktop applications using traditional installers. The Microsoft Store on Windows has long had great support for UWP apps, PWAs, and desktop apps packaged in.