Ekhlass/Flutter_Documentation · Datasets at Hugging Face

text stringlengths 1 474
push notifications), and you can start adding add-ons.Options such as pricing, availability,
age ratings, and category have to be
configured together with the first submission
and are automatically retained
for the subsequent submissions.<topic_end>
<topic_start>
Packaging and deployment
In order to publish an application to Microsoft Store,
you must first package it.
The valid formats are .msix, .msixbundle,
.msixupload, .appx, .appxbundle,
.appxupload, and .xap.<topic_end>
<topic_start>
Manual packaging and deployment for the Microsoft Store
Check out MSIX packaging
to learn about packaging
Flutter Windows desktop applications.Note that each product has a unique identity,
which the Store assigns.If the package is being built manually,
you have to include its identity details
manually during the packaging.
The essential information can be retrieved
from the Partner Center using the following instructions:After manually packaging the application,
manually submit it to the
Microsoft Partner Center.
You can do this by creating a new submission,
navigating to Packages,
and uploading the created application package.<topic_end>
<topic_start>
Continuous deployment
In addition to manually creating and deploying the package,
you can automate the build, package, versioning,
and deployment process using CI/CD tooling after having submitted
the application to the Microsoft Store for the first time.<topic_end>
<topic_start>Codemagic CI/CD
Codemagic CI/CD uses the
msix pub package to package
Flutter Windows desktop applications.For Flutter applications, use either the
Codemagic Workflow Editor
or codemagic.yaml
to package the application and deploy it
to the Microsoft Partner Center.
Additional options (such as the list of
capabilities and language resources
contained in the package)
can be configured using this package.For publishing, Codemagic uses the
Partner Center submission API;
so, Codemagic requires
associating the Azure Active Directory
and Partner Center accounts.<topic_end>
<topic_start>GitHub Actions CI/CD
GitHub Actions can use the
Microsoft Dev Store CLI
to package applications into an MSIX and publish them to the Microsoft Store.
The setup-msstore-cli
GitHub Action installs the cli so that the Action can use it for packaging
and publishing.As packaging the MSIX uses the
msix pub package, the project’s pubspec.yaml
must contain an appropriate msix_config node.You must create an Azure AD directory from the Dev Center with
global administrator permission.The GitHub Action requires environment secrets from the partner center.
AZURE_AD_TENANT_ID, AZURE_AD_ClIENT_ID, and AZURE_AD_CLIENT_SECRET
are visible on the Dev Center following the instructions for the
Windows Store Publish Action.
You also need the SELLER_ID secret, which can be found in the Dev Center
under Account Settings > Organization Profile > Legal Info.The application must already be present in the Microsoft Dev Center with at
least one complete submission, and msstore init must be run once within
the repository before the Action can be performed. Once complete, running
msstore package .
and
msstore publish
in a GitHub Action packages the
application into an MSIX and uploads it to a new submission on the dev center.The steps necessary for MSIX publishing resemble the following<topic_end>
<topic_start>
Updating the app’s version number
For apps published to the Microsoft Store,
the version number must be set during the
packaging process.The default version number of the app is 1.0.0.0.info Note
Microsoft Store apps are not allowed to have a
Version with a revision number other than zero.
Therefore, the last number of the version must
remain zero for all releases.
Ensure that you follow Microsoft’s
versioning guidelines.For apps not published to the Microsoft Store, you
can set the app’s executable’s file and product versions.
The executable’s default file version is 1.0.0.1,
and its default product version is 1.0.0+1. To update these,
navigate to the pubspec.yaml file and update the
following line:The build name is three numbers separated by dots,
followed by an optional build number that is separated
by a +. In the example above, the build name is 1.0.0
and the build number is 1.The build name becomes the first three numbers of the
file and product versions, while the build number becomes
the fourth number of the file and product versions.Both the build name and number can be overridden in
flutter build windows by specifying --build-name and
--build-number, respectively.info Note
Flutter projects created before Flutter 3.3
need to be updated to set the executable’s version
information. For more information,
refer to the version migration guide.<topic_end>
<topic_start>
Add app icons

push notifications), and you can start adding add-ons.Options such as pricing, availability,

age ratings, and category have to be

configured together with the first submission

and are automatically retained

for the subsequent submissions.<topic_end>

<topic_start>

Packaging and deployment

In order to publish an application to Microsoft Store,

you must first package it.

The valid formats are .msix, .msixbundle,

.msixupload, .appx, .appxbundle,

.appxupload, and .xap.<topic_end>

<topic_start>

Manual packaging and deployment for the Microsoft Store

Check out MSIX packaging

to learn about packaging

Flutter Windows desktop applications.Note that each product has a unique identity,

which the Store assigns.If the package is being built manually,

you have to include its identity details

manually during the packaging.

The essential information can be retrieved

from the Partner Center using the following instructions:After manually packaging the application,

manually submit it to the

Microsoft Partner Center.

You can do this by creating a new submission,

navigating to Packages,

and uploading the created application package.<topic_end>

<topic_start>

Continuous deployment

In addition to manually creating and deploying the package,

you can automate the build, package, versioning,

and deployment process using CI/CD tooling after having submitted

the application to the Microsoft Store for the first time.<topic_end>

<topic_start>Codemagic CI/CD

Codemagic CI/CD uses the

msix pub package to package

Flutter Windows desktop applications.For Flutter applications, use either the

Codemagic Workflow Editor

or codemagic.yaml

to package the application and deploy it

to the Microsoft Partner Center.

Additional options (such as the list of

capabilities and language resources

contained in the package)

can be configured using this package.For publishing, Codemagic uses the

Partner Center submission API;

so, Codemagic requires

associating the Azure Active Directory

and Partner Center accounts.<topic_end>

<topic_start>GitHub Actions CI/CD

GitHub Actions can use the

Microsoft Dev Store CLI

to package applications into an MSIX and publish them to the Microsoft Store.

The setup-msstore-cli

GitHub Action installs the cli so that the Action can use it for packaging

and publishing.As packaging the MSIX uses the

msix pub package, the project’s pubspec.yaml

must contain an appropriate msix_config node.You must create an Azure AD directory from the Dev Center with

global administrator permission.The GitHub Action requires environment secrets from the partner center.

AZURE_AD_TENANT_ID, AZURE_AD_ClIENT_ID, and AZURE_AD_CLIENT_SECRET

are visible on the Dev Center following the instructions for the

Windows Store Publish Action.

You also need the SELLER_ID secret, which can be found in the Dev Center

under Account Settings > Organization Profile > Legal Info.The application must already be present in the Microsoft Dev Center with at

least one complete submission, and msstore init must be run once within

the repository before the Action can be performed. Once complete, running

msstore package .

and

msstore publish

in a GitHub Action packages the

application into an MSIX and uploads it to a new submission on the dev center.The steps necessary for MSIX publishing resemble the following<topic_end>

<topic_start>

Updating the app’s version number

For apps published to the Microsoft Store,

the version number must be set during the

packaging process.The default version number of the app is 1.0.0.0.info Note

Microsoft Store apps are not allowed to have a

Version with a revision number other than zero.

Therefore, the last number of the version must

remain zero for all releases.

Ensure that you follow Microsoft’s

versioning guidelines.For apps not published to the Microsoft Store, you

can set the app’s executable’s file and product versions.

The executable’s default file version is 1.0.0.1,

and its default product version is 1.0.0+1. To update these,

navigate to the pubspec.yaml file and update the

following line:The build name is three numbers separated by dots,

followed by an optional build number that is separated

by a +. In the example above, the build name is 1.0.0

and the build number is 1.The build name becomes the first three numbers of the

file and product versions, while the build number becomes

the fourth number of the file and product versions.Both the build name and number can be overridden in

flutter build windows by specifying --build-name and

--build-number, respectively.info Note

Flutter projects created before Flutter 3.3

need to be updated to set the executable’s version

information. For more information,

refer to the version migration guide.<topic_end>

<topic_start>

Add app icons