VijayAnand.BlazorTemplates 4.0.0

The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org. Prefix Reserved
This package has a SemVer 2.0.0 package version: 4.0.0+sha.755342d. 
dotnet new install VijayAnand.BlazorTemplates::4.0.0
This package contains a .NET Template Package you can call from the shell/command line.

Blazor desktop project template

A project template for hosting the Blazor component in the Windows Forms and WPF desktop application.

To install the template package:

dotnet new install VijayAnand.BlazorTemplates

To update the template package:

dotnet new update --check-only

dotnet new update

To make use of the template:

By default, this creates a solution that targets .NET 8.

For WinForms:

dotnet new winforms-blazor

For WPF:

dotnet new wpf-blazor

To target .NET 6 / .NET 7 / .NET 9, pass the corresponding value (net6.0 / net7.0 / net9.0) to the framework (--framework | -f) parameter, example shown below.

dotnet new winforms-blazor -f net7.0

dotnet new winforms-blazor -f net9.0

dotnet new wpf-blazor -f net7.0

dotnet new wpf-blazor -f net9.0

Optionally, to abstract Razor components as a separate Razor Class Library (RCL), pass the below parameter while creating the project:

-rcl | --razor-class-library - Default value is false

For WinForms:

dotnet new winforms-blazor -rcl

For WPF:

dotnet new wpf-blazor -rcl

Optionally, to make use of NuGet Central Package Management (CPM) feature, pass the below parameter while creating the project (Supported from v3.5.0 onwards):

-cpm | --central-pkg-mgmt - Default value is false

For WinForms:

dotnet new winforms-blazor -cpm

For WPF:

dotnet new wpf-blazor -cpm

Has support for Item Templates too:

  • Windows Form with BlazorWebView
    • Named as winforms-bwv
  • WPF Window with BlazorWebView
    • Named as wpf-bwv

Both of these templates require a parameter:

  • -n | --name - The Name of the Item to create

Note:

Ensure the project dependencies are restored before creating Item from these templates.

dotnet new winforms-bwv -n MyForm

dotnet new wpf-bwv -n MyWindow

To uninstall the template package:

dotnet new uninstall VijayAnand.BlazorTemplates

  • .NETStandard 2.0

    • No dependencies.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
4.0.0 935 2/15/2024
3.6.1 714 1/18/2024
3.6.0 227 1/11/2024
3.5.0 1,533 11/14/2023
3.5.0-preview.1 669 10/19/2023
3.4.0 242 10/12/2023
3.3.0 96 9/14/2023
3.2.4 101 8/14/2023
3.2.3 107 7/16/2023
3.2.2 100 6/14/2023
3.2.1 89 5/19/2023
3.2.0 119 4/12/2023
3.2.0-preview.2 77 4/4/2023
3.2.0-preview.1 78 4/1/2023
3.1.0 105 3/27/2023
3.0.3 95 3/25/2023
3.0.2 94 3/24/2023
3.0.1 93 3/15/2023
3.0.0 104 2/21/2023
2.2.0 959 12/16/2022
2.1.1 312 11/23/2022
2.1.0 344 11/8/2022
2.0.0 387 10/5/2022
1.2.0 544 6/14/2022
1.1.0 461 5/23/2022
1.0.14 446 5/12/2022
1.0.13 484 4/28/2022
1.0.12 452 4/18/2022
1.0.11 450 4/12/2022
1.0.10 435 3/18/2022
1.0.9 397 2/18/2022
1.0.8 424 2/17/2022
1.0.7 418 2/7/2022
1.0.6 365 12/17/2021
1.0.5 357 11/19/2021
1.0.4 281 11/12/2021
1.0.3 288 11/9/2021
1.0.2 368 10/15/2021
1.0.1 353 9/16/2021
1.0.0 769 8/18/2021

Join me on Developer Thoughts (https://egvijayanand.in/), an exclusive blog for articles on .NET MAUI and Blazor.

What's new in ver. 4.0.0:
-------------------------
1. Support for creating .NET Blazor Hybrid projects on .NET 9 Previews.

For this, have introduced an additional option to the framework parameter - net9.0

Note: The default value for the framework parameter remains as net8.0, which means to create a project for .NET 9, an explicit value of net9.0 is to be passed.

dotnet new winforms-blazor -o MyApp -f net9.0

dotnet new wpf-blazor -o MyApp -f net9.0

2. WPF Blazor namespace updated to URI based.

v3.6.1:

Updated the WinForms and WPF Blazor hybrid NuGet package reference to .NET MAUI 8 SR1 (8.0.6)

For more details, check this article:

https://egvijayanand.in/2024/01/18/dotnet-maui-8-service-release-1/

v3.6.0:

Source file namespace for BlazorWebView item templates automatically resolved from root namespace.

v3.5.0:

Templates updated for .NET 8 RTM.

Preview feature is now stable.

Note: For now, the CPM feature is only supported on CLI.

v3.5.0-preview.1:

Introduced an option for NuGet Central Package Management in CLI project templates.

-cpm | --central-pkg-mgmt - The default value is false.

dotnet new winforms-blazor -o MyApp -cpm

dotnet new wpf-blazor -o MyApp -cpm

v3.4.0

Templates updated for .NET 8 RC2.

v3.3.0:

Templates updated for .NET 8 RC1.

The default value for the Framework parameter (--framework / -f) is now updated as net8.0

v3.2.4:

Templates updated for .NET 8 Preview 7.

v3.2.3:

Templates updated for .NET 8 Preview 6.

v3.2.2:

Templates updated for .NET 8 Preview 5.

v3.2.1:

Templates updated for .NET 8 Preview 4.

v3.2.0:

All the preview features have reached stable.

Templates updated for .NET 8 Preview 3.

Item template for the following:

Windows Form with BlazorWebView:

dotnet new winforms-bwv -n MyForm -na BlazorApp

WPF Window with BlazorWebView:

dotnet new wpf-bwv -n MyWindow -na BlazorApp

Note:

Ensure the project dependencies are restored before creating Item from these templates.

While working with .NET 7 or higher SDK, the namespace parameter in short notation needs to be passed as -p:na (i.e., it needs to be prefixed with -p:).

v3.2.0-preview.2:

An option to abstract the Razor components as a separate Razor class library.

-rcl | --razor-class-library - Default value is false

dotnet new winforms-blazor -n MyApp -rcl
(or)
dotnet new winforms-blazor --name MyApp --razor-class-library

dotnet new wpf-blazor -n MyApp -rcl
(or)
dotnet new wpf-blazor --name MyApp --razor-class-library

v3.2.0-preview.1:

Template restructured to follow the same sample as other App Models.

v3.1.0:

1. Added the open-iconic artifacts to the solution

2. While targeting .NET 8, the StartPath property is set to load a Razor component other than the one defined with default route address of '/'

v3.0.3:

1. Added the option to allow for restore/build action on Windows projects on non-Windows platforms.

-ewt | --enable-windows-targeting

2. In Windows Forms solution, the Router component is renamed as Main.razor for better interop with other AppModels.

dotnet new winforms-blazor -ewt

dotnet new wpf-blazor -ewt

v3.0.2:

Added the option to skip creating a solution file.

-nsf | --no-solution-file - Default value is false

dotnet new winforms-blazor -nsf

dotnet new wpf-blazor -nsf

v3.0.1:

Templates updated for .NET 8 Preview 2.

v3.0.0:

Templates updated for .NET 8 Preview 1.

Supported values for target framework parameter, can be specified with --framework / -f

net6.0
net7.0 (the default value)
net8.0

Examples:

dotnet new winforms-blazor -f net8.0 -o BlazorWinForms1

dotnet new wpf-blazor -f net8.0 -o BlazorWpf1

v2.2.0:

Templates updated for .NET 7 service release.

The Blazor hybrid package version is updated as a wildcard so that the latest stable version will be pulled from the NuGet repository.

.NET 7 - 7.0.*

.NET 6 - 6.0.*

v2.1.1:

A little housekeeping to improve the reliability of the templates.

v2.1.0:

Templates updated for .NET 7 GA release.

Blazor desktop templates for Windows Forms and WPF.

Currently targeting .NET 6 / 7 and the corresponding .NET MAUI release.

A parameter named framework has been introduced that takes either net6.0 or net7.0 as its options (with net7.0 being the default value).

dotnet new winforms-blazor --framework net6.0

dotnet new winforms-blazor -f net7.0

dotnet new wpf-blazor --framework net6.0

dotnet new wpf-blazor -f net7.0

Unified template now also available as a VS extension.

https://marketplace.visualstudio.com/items?itemName=egvijayanand.blazor-desktop-templates

Take a look at this Blazor article for working with these templates:

https://egvijayanand.in/2021/11/13/net-maui-blazor/