Document integrating build-generated files into static web assets - #37545
Open
wadepickett with Copilot wants to merge 7 commits into
Open
Document integrating build-generated files into static web assets#37545wadepickett with Copilot wants to merge 7 commits into
wadepickett with Copilot wants to merge 7 commits into
Conversation
Co-authored-by: wadepickett <10985336+wadepickett@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Provide guidance on integrating build generated files into Static Web Assets
Document integrating build-generated files into static web assets
Aug 26, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the Static files in ASP.NET Core documentation to add guidance for incorporating build-generated outputs (for example, TypeScript/bundled JavaScript) into the .NET 9+ static web assets / MapStaticAssets pipeline so they can benefit from fingerprinting, compression, and caching.
Changes:
- Adds a new Integrate build-generated files into static web assets section under the
>= aspnetcore-9.0content, documenting the<Content Link=...>approach and the.esproj/Microsoft.VisualStudio.JavaScript.Sdkapproach. - Makes broad editorial refinements throughout the article (rewording several paragraphs/headings).
- Updates
ms.date.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Co-authored-by: wadepickett <10985336+wadepickett@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
wadepickett
marked this pull request as ready for review
August 27, 2026 00:22
wadepickett
approved these changes
Aug 27, 2026
Contributor
maraf
reviewed
Aug 27, 2026
Per review feedback: Clarify how build-generated files are included as static web assets and update the explanation regarding files resolved under `wwwroot`.
Per review feedback: Clarified that the generated file must exist before resolving static web assets.
Contributor
|
@maraf, thanks for the great review suggestions. I have updated accordingly. Could you take a look and see if is good to go? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fundamentals/static-files.mdhad no guidance for getting build-generated files (TypeScript output, bundled JS, or any custom build output) into the Map Static Assets pipeline so they gain fingerprinting, compression, and caching. This adds a section documenting the two maintainer-confirmed approaches (see dotnet/runtime#118146).Changes
## Integrate build-generated files into static web assetssection inaspnetcore/fundamentals/static-files.md, within the>= aspnetcore-9.0block, after "Static assets manifest" (where readers learn that files outside the build-time web root aren't served). Covers:<Content>item withLinkmetadata so a file stored outsidewwwrootis discovered as a static web asset, plus a note that the file must exist when static web assets are resolved.Microsoft.VisualStudio.JavaScript.Sdk(.esproj) project referenced by the app, with thefluentui-blazorAssets project as an example.ms.date.Link approach example
Notes
ResolveCurrentProjectStaticWebAssetsInputsDependsOn), which the triage flagged as unverified for .NET 9+; the documented<Content Link>and.esprojpaths are the ones confirmed by the runtime team.Internal previews