[release/8.0-preview4] [wasm] GenerateWasmBootJson - close file handles #85482
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.
Backport of #85480 to release/8.0-preview4
/cc @lewing @radical
Customer Impact
Blazor hosted templates will fail to publish during the nested build process.
Expected to fix the failures found in dotnet/aspnetcore#47540 (comment) .
Background
The hypothesis is that the following operations happen in order:
GenerateBlazorBootExtensionJson
callsFile.Create
to createobj/Release/net8.0/blazor.publish.boot-extension.json
, and the file handle is closedGenerateWasmBootJson
opens the same file withFile.OpenRead
but does not close itGenerateBlazorBootExtensionJson
runs again as part of the nested build, but fails because (2) left the file openTesting
Automated and manual verification that the change is correct and doesn't regress working scenarios.
Risk
Very low, the change is very small and tested