Skip to content

[Blazor] Handle the concept of generated static web assets within Razor/Blazor #24245

@javiercn

Description

@javiercn

Currently there are three types of static web assets sources '' (current project), "Project", "Package". This is problematic for Blazor webassembly apps where we generate assets for the current project on locations different than wwwroot.

This is problematic for standalone apps but it can also be problematic for generated files on the host (which we don't have yet).

We can introduce the concept of "Generated" static web assets, which belong to the project, but get considered for publish and similar scenarios.

Currently we hack around with internals to make this work on the build.

Metadata

Metadata

Assignees

Labels

DoneThis issue has been fixedarea-blazorIncludes: Blazor, Razor Componentsarea-mvcIncludes: MVC, Actions and Controllers, Localization, CORS, most templatesenhancementThis issue represents an ask for new feature or an enhancement to an existing onefeature-static-web-assets

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions