Datasets:
Ekhlass
/
flutter_docs

Dataset card Data Studio Files
xet
 Community
1
text
stringlengths
1
372
additional resources
you can learn more from the following links on the
snapcraft.io site:
<topic_end>
<topic_start>
build and release a windows desktop app
one convenient approach to distributing windows apps
is the microsoft store.
this guide provides a step-by-step walkthrough
of packaging and deploying a flutter app in this way.
info note
you are not required to publish windows apps through the
microsoft store, particularly if you prefer more control
over the distribution experience or don’t want to deal
with the certification process. the microsoft documentation
includes more information about traditional installation
approaches, including windows installer.
<topic_end>
<topic_start>
preliminaries
before beginning the process of releasing
a flutter windows desktop app to the microsoft store,
first confirm that it satisfies microsoft store policies.
also, you must join the
microsoft partner network to be able to submit apps.
<topic_end>
<topic_start>
set up your application in the partner center
manage an application’s life cycle in the
microsoft partner center.
first, reserve the application name and
ensure that the required rights to the name exist.
once the name is reserved, the application
will be provisioned for services (such as
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.