forked from dotnet/runtime
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[wasm] Allow selecting which target to run before, for nested publish
Part of fix for dotnet#60479 . The other part of the fix will be in `dotnet/sdk`. - Currently for the nested publish, we run `Publish`, and then our native targets. But that can be an overkill, and can cause issues like the one being fixed here. - Instead, allow blazor to configure which target to run instead, which would provide us with the correct set of inputs. - In future, this will be cleaned up, and implemented differently. - Also, a fixed up copy of `Microsoft.NET.Sdk.BlazorWebAssembly.6_0.targets` is included here, so we can run the corresponding test. And it can be removed once the SDK part of the fix gets merged.
- Loading branch information
Showing
3 changed files
with
57 additions
and
2 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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