BlazorWebView packaging change proposal

[Eilon]

There was a recent discussion about ideas on changing how BlazorWebView is packaged. Right now to use BlazorWebView you have to reference a package, set your project to use an SDK, and potentially some other settings. We can hide much of that via targets/props in the package, but we want to consider having something like UseBlazorWebView as an MSBuild property. To solve everything we need to consider changes to the Razor SDK to be always-imported (but perhaps only conditionally enabled).

Ideas:

• Always import Razor SDK props
• Only import targets is UseBlazorWebView is set
• Change to a Framework Pack

[Daniellled]

This brings up a good question. I see we still have two project templates

dotnet new maui
and
dotnet new maui-blazor

Are you proposing that only one project template exist
dotnet new maui
And if you need to use BlazorWebview you can include the package?

[Eilon]

@Daniellled I think there would still be 2 templates because they would have different contents. But we could possibly make it easier to add BlazorWebView to an existing .NET MAUI project with these suggestions.

[mkArtakMSFT]

@Eilon closing this as our template story is finalized at this point. Let us know if you want to discuss this.