8000 There doesn't appear to be an easy way to disable StaticWebAssets caching functionality · Issue #48985 · dotnet/sdk · GitHub
[go: up one dir, main page]
Skip to content

There doesn't 8000 appear to be an easy way to disable StaticWebAssets caching functionality #48985

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
breidikl opened this issue May 15, 2025 · 2 comments · Fixed by #49020
Closed

There doesn't appear to be an easy way to disable StaticWebAssets caching functionality #48985

breidikl opened this issue May 15, 2025 · 2 comments · Fixed by #49020

Comments

@breidikl
Copy link
breidikl commented May 15, 2025 •
edited
Loading

When updating the SDK from 9.0.203 to 9.0.300 we see new rpswa.dswa.cache.json StaticWebAsset caching files being created that cause multi-write issues when running under BuildXL.

There doesn't appear to be a way to easily disable this functionality. Untracking the file results in UnauthorizedAccessException errors, as it appears multiple processes try to update the cache file at the same time though the first process locks the file.

This appears to have been added via 7bf5e9f so mentioning @javiercn
@dotnet-policy-service dotnet-policy-service bot added the untriaged Request triage from a team member label May 15, 2025
@javiercn
Copy link
Member
javiercn commented May 15, 2025 •
edited
Loading

@breidikl thanks for raising this up.

Can you try adding <StaticWebAssetsEnabled>false</StaticWebAssetsEnabled> into the project?

@breidikl
Copy link
Author

I've confirmed disabling StaticWebAssets resolves the issues, after following up with that those teams did not need the functionality.

@javiercn javiercn mentioned this issue May 16, 2025
Merged
@dotnet-policy-service dotnet-policy-service bot removed the untriaged Request triage from a team member label May 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@javiercn @breidikl
0