Windows with .NET CLI or VS Code

Use this workflow if you prefer command-line project creation, work in Visual Studio Code, or want to inspect the template output directly. The same dotnet commands work from a terminal, from VS Code's integrated terminal, or from any editor that opens the generated project folder.

Requirements

  • Windows x64
  • .NET SDK 8+
  • CMake and Ninja available on PATH
  • A C++ toolchain

CMake, Ninja, and the C++ toolchain are used by the bridge build behind the scenes; you do not need to write CMake files or C++ code for a template project. On Windows, the C++ toolchain usually comes from Visual Studio or the Visual Studio Build Tools C++ workload.

Create a project from templates

Install the templates:

dotnet new install QtGroup.Qt.Bridge.CSharp.Templates

Create, build, and run a project:

dotnet new qt -n MyQtApp
cd MyQtApp
dotnet build
dotnet run

For template options such as --Framework and --SampleCode, generated project structure, and QML item templates, see Project Templates.

Add Qt Bridge for C# to an existing project

For an existing Windows x64 project, add the Windows package:

dotnet add package QtGroup.Qt.Bridge.CSharp.win-x64 --version 0.3.*-*

The package is platform-specific because the bridge includes native runtime pieces for the target platform. The 0.3.*-* version range stays on the 0.3 pre-release train.

Then build and run from the command line or your editor:

dotnet build
dotnet run

For the full migration workflow, including QML files, startup calls, and exposing your existing C# objects to QML, see Adding QML to Existing C# Projects.

Check your setup

After the first build, check that:

  • The project builds without missing toolchain errors
  • The application launches
  • QML files are present in the project folder
  • The project contains the expected C# entry point and Main.qml

Common first issues

If the project does not build or run, check these areas first:

  • The .NET SDK is missing or older than .NET 8
  • The C++ toolchain is not installed or not available to the build
  • The selected package or runtime does not match Windows x64
  • The terminal is not running from the project directory