-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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.
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
[Blazor] Update the base path to use IntermediateOutputPath #26765
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks plausible, but I don't have any context on why it wasn't already done in this simpler way before.
Also since there are no tests for this I'm trusting you've done whatever level of verification is necessary!
@SteveSandersonMS thanks. It was done a different way because a while ago we were computing the path inside a global PropertyGroup and when we changed it to be computed inside a target (as it should have been done from the beginning) we (I) didn't clean it up to just rely on the IntermediateOutputPath. Pretty much every test covers this scenario, which is a good indication that nothing has changed. The part where this will help a bit is on the Maui side, where the platform wasn't being included on the output. However, it is a bit complicated to author a test for that here. |
/backport to release/6.0.4xx |
It was done a different way because a while ago we were computing the path inside a global PropertyGroup and when we changed it to be computed inside a target, we didn't change it to just rely on the IntermediateOutputPath. (cherry picked from commit ab4d89f)
* [Blazor] Update the base path to use IntermediateOutputPath (#26765) It was done a different way because a while ago we were computing the path inside a global PropertyGroup and when we changed it to be computed inside a target, we didn't change it to just rely on the IntermediateOutputPath. (cherry picked from commit ab4d89f) * [Blazor] Allow customizing the static web assets base manifest paths if defined by the environment (#27102) (cherry picked from commit bcb1cd2) Co-authored-by: Javier Calvarro Nelson <jacalvar@microsoft.com>
We can rely on IntermediateOutputPath here since we moved computing these values to a target.
Fixes #26762