Init Command
Helps you setup your application to publish to the Microsoft Store.
Description
The init
command helps you setup your application to publish to the Microsoft Store. It currently supports the following application types:
- Windows App SDK/WinUI 3
- UWP
- .NET MAUI
- Flutter
- Electron
- React Native for Windows
- PWA
Usage Examples
Windows App SDK/WinUI 3
msstore init "C:\path\to\winui3_app"
UWP
msstore init "C:\path\to\uwp_app"
.NET MAUI
msstore init "C:\path\to\maui_app"
Flutter
msstore init "C:\path\to\flutter_app"
Electron
msstore init "C:\path\to\electron_app"
React Native for Windows
msstore init "C:\path\to\react_native_app"
Note
For Electron, as well as React Native for Windows projects, both Npm
and Yarn
are supported. The presence of the Yarn
lock file (yarn.lock
) will be used to determine which package manager to use, so make sure that you check in your lock file into your source control system.
PWA
msstore init https://contoso.com --output .
Arguments
Argument | Description |
---|---|
pathOrUrl |
The root directory path where the project file is, or a public URL that points to a PWA. |
Options
Option | Description |
---|---|
-n, --publisherDisplayName | The Publisher Display Name used to configure the application. If provided, avoids an extra APIs call. |
--package | If supported by the app type, automatically packs the project. |
--publish | If supported by the app type, automatically publishes the project. Implies '--package true' |
-a, --arch | The architecture(s) to build for. If not provided, the default architecture for the current OS, and project type, will be used. Allowed values: "x86", "x64", "arm64". Only used it used in conjunction with '--package true'. |
-o, --output | The output directory where the packaged app will be stored. If not provided, the default directory for each different type of app will be used. |
-ver, --version | The version used when building the app. If not provided, the version from the project file will be used. |
Collaborate with us on GitHub
The source for this content can be found on GitHub, where you can also create and review issues and pull requests. For more information, see our contributor guide.
Windows developer
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for