Migrate a Windows project to set version information

Contents

Migration steps
Example

Flutter 3.3 added support for setting the Windows app’s version from the pubspec.yaml file or through the --build-name and --build-number build arguments. For more information, refer to the Build and release a Windows app documentation.

Projects created before Flutter version 3.3 need to be migrated to support versioning.

Migration steps

Your project can be updated using these steps:

Verify you are on Flutter version 3.3 or newer using flutter --version
If needed, use flutter upgrade to update to the latest version of the Flutter SDK
Backup your project, possibly using git or some other version control system
Delete the windows/runner/CMakeLists.txt and windows/runner/Runner.rc files
Run flutter create --platforms=windows .
Review the changes to your windows/runner/CMakeLists.txt and windows/runner/Runner.rc files
Verify your app builds using flutter build windows

Note: Follow the run loop migration guide if the build fails with the following error message:

  flutter_window.obj : error LNK2019: unresolved external symbol "public: void __cdecl RunLoop::RegisterFlutterInstance(class flutter::FlutterEngine *)" (?RegisterFlutterInstance@RunLoop@@QEAAXPEAVFlutterEngine@flutter@@@Z) referenced in function "protected: virtual bool __cdecl FlutterWindow::OnCreate(void)" (?OnCreate@FlutterWindow@@MEAA_NXZ)

Example

PR 721 shows the migration work for the Flutter Gallery app.