Blazor Hybrid Windows Desktop Templates

Blazor Hybrid Windows Desktop Templates for Visual Studio 2022 and 2026 Insiders

Project template for hosting the Blazor component in the Windows Forms and WPF Desktop application targeting the Windows platform.

Consult this article for more details on this Blazor Hybrid Windows Desktop Templates.

Stay connected with my Developer Thoughts blog for detailed insights on .NET MAUI and Blazor.

The VS extension is now supported on both x64 and ARM64 installations of Visual Studio 2022 (v4.3.0.0 or higher) and 2026 Insiders release (v6.6.0.0). Happy coding!

Consequently, the minimum supported version of Visual Studio 2022 will be v17.6 or higher.

The v6.6.0.0 VS extension is now compatible with the Visual Studio 2026 Insiders release v18.0.0

Version History (latest on top):

6.6.0.0:

• First and foremost, adding support for the Visual Studio 2026 Insiders release.
• Templates updated to support .NET 10 RC1.

6.5.0.0:

• Templates updated to support .NET 10 Preview 7.

6.4.0.0:

• Templates updated to support .NET 10 Preview 6.

6.3.0.0:

• Templates updated to support .NET 10 Preview 5.

6.2.0.0:

• Templates updated to support .NET 10 Preview 4.

6.0.0.0:

• Support for creating .NET Blazor Hybrid Window Desktop projects on .NET 10 Previews.
  • For this, have introduced an additional option to the Framework parameter - .NET 10 (Preview).

Note: The default value for the Framework parameter remains as .NET 9 (STS).

5.0.0.0:

• Templates updated to support .NET 9 Stable channel release.
  • The default value for the Framework parameter is now set to .NET 9 (STS).
  • So by default, the project command generates a .NET 9 project.
• To create a .NET 8 project, explicitly select the value .NET 8 (LTS) for the Framework parameter.
• Removed out-of-support versions (.NET 6 and 7).

4.5.0.0:

• Templates updated to support the .NET 9 RC2 release.

4.4.0.0:

• Templates updated to support the .NET 9 RC1 release.
• Introduced an option to add a reference to the CommunityToolkit.Mvvm NuGet package to work with MVVM.

4.3.0.0:

• The Blazor Desktop Templates Pack VS extension is now supported on both x64 and ARM64 installations of Visual Studio 2022. Happy coding!
  • Consequently, the minimum supported version of VS2022 will be v17.6 or higher.
• Templates updated to support .NET 9 Preview 7 and the latest .NET 8 release.
• Introduced an option to support the XML-based solution file (slnx) format.
  • This would be an explicit option since the SLNX feature is currently in the preview stage and is only supported on VS2022.

4.2.0.0:

• Introduced using the NuGet CPM feature from within Visual Studio IDE
• Templates updated to support .NET 9 Preview 5 and the latest .NET 8 release

4.1.0.0:

• Templates updated to support .NET 9 Preview 4 and the latest .NET 8 release

4.0.0.0:

• Support for creating .NET Blazor Hybrid projects on .NET 9 Previews
• WPF Blazor namespace updated to URI-based

3.6.1.0:

• Updated the WinForms and WPF Blazor hybrid NuGet package reference to .NET MAUI 8 SR1 (8.0.6)
  • For more details, check this article

3.5.0.0:

• Templates updated for .NET 8 RTM

3.4.0.0:

• Templates updated for .NET 8 RC2

3.3.0.0:

• Templates updated for .NET 8 RC1
• The default value for the Framework parameter is now updated as net8.0

3.2.4.0:

• Templates updated for .NET 8 Preview 7.

3.2.3.0:

• Templates updated for .NET 8 Preview 6.

3.2.2.0:

• Templates updated for .NET 8 Preview 5.

3.2.1.0:

• Templates updated for .NET 8 Preview 4.

3.2.0.0:

• Template restructured to follow the same sample as other App Models.
• Templates updated to support .NET 8 Preview 3.
• Item templates for Windows Form with BlazorWebView and WPF Window with BlazorWebView.
• An option to create a separate Razor Class Library (RCL) to abstract the Razor components.
  • -rcl | --razor-class-library - Default value is false

3.1.0.0:

• Added the open-iconic artifacts to the solution
• While targeting .NET 8, the StartPath property is set to load a Razor component other than the one defined with the default route address of /
• In Windows Forms solution, the Router component is renamed as Main.razor for better interop with other AppModels