Datasets:
Ekhlass
/
flutter_docs

Dataset card Data Studio Files
xet
Community
1
text
stringlengths
1
372
copyright information and application version that
is embedded in the windows app, which is displayed
in the windows explorer properties dialog box.
to change the version number, edit the VERSION_AS_NUMBER
and VERSION_AS_STRING properties;
other information can be edited in the StringFileInfo block.
<topic_end>
<topic_start>
compiling with visual studio
for most apps, it’s sufficient to allow flutter to
handle the compilation process using the flutter run
and flutter build commands. if you are making significant
changes to the runner app or integrating flutter into an existing app,
you might want to load or compile the flutter app in visual studio itself.
follow these steps:
run flutter build windows to create the build\ directory.
open the visual studio solution file for the windows runner,
which can now be found in the build\windows directory,
named according to the parent flutter app.
in solution explorer, you will see a number of projects.
right-click the one that has the same name as the flutter app,
and choose set as startup project.
to generate the necessary dependencies,
run build > build solution
you can also press/
ctrl + shift + b.
to run the windows app from visual studio, go to debug > start debugging.
you can also press f5.
use the toolbar to switch between debug and release
configurations as appropriate.
<topic_end>
<topic_start>
distributing windows apps
there are various approaches you can use for
distributing your windows application.
here are some options:
<topic_end>
<topic_start>
MSIX packaging
MSIX, the new windows application package format,
provides a modern packaging format and installer.
this format can either be used to ship applications
to the microsoft store on windows, or you can
distribute app installers directly.
the easiest way to create an MSIX distribution
for a flutter project is to use the
msix pub package.
for an example of using the msix package
from a flutter desktop app,
see the desktop photo search sample.
<topic_end>
<topic_start>
create a self-signed .pfx certificate for local testing
for private deployment and testing with the help
of the MSIX installer, you need to give your application a
digital signature in the form of a .pfx certificate.
for deployment through the windows store,
generating a .pfx certificate is not required.
the windows store handles creation and management
of certificates for applications
distributed through its store.
distributing your application by self hosting it on a
website requires a certificate signed by a
certificate authority known to windows.
use the following instructions to generate a
self-signed .pfx certificate.
<topic_end>
<topic_start>
building your own zip file for windows
the flutter executable, .exe, can be found in your
project under build\windows\runner\<build mode>\.
in addition to that executable, you need the following:
place the DLL files in the directory next to the executable
and the other DLLs, and bundle them together in a zip file.
the resulting structure looks something like this:
at this point if desired it would be relatively simple to
add this folder to a windows installer such as inno setup, WiX, etc.
<topic_end>
<topic_start>
using packages
flutter supports using shared packages contributed by other developers
to the flutter and dart ecosystems. this allows quickly building
an app without having to develop everything from scratch.
what is the difference between a package
and a plugin? a plugin is a type of
package—the full designation is plugin package,
which is generally shortened to plugin.
existing packages enable many use cases—for example,
making network requests (http),
navigation/route handling (go_router),
integration with device APIs
(url_launcher and battery_plus),
and using third-party platform SDKs like firebase
(flutterfire).
to write a new package, see developing packages.
to add assets, images, or fonts,
whether stored in files or packages,
see adding assets and images.
<topic_end>
<topic_start>