Skip to content

BlazorWebView packaging change proposal #1283

@Eilon

Description

@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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions