Skip to content
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

Merged
merged 1 commit into from
Jul 25, 2022

Conversation

javiercn
Copy link
Member

We can rely on IntermediateOutputPath here since we moved computing these values to a target.

Fixes #26762

@dotnet-issue-labeler dotnet-issue-labeler bot added the Area-AspNetCore RazorSDK, BlazorWebAssemblySDK, dotnet-watch label Jul 22, 2022
@javiercn javiercn requested a review from a team July 25, 2022 13:47
Copy link
Member

@SteveSandersonMS SteveSandersonMS left a 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!

@javiercn
Copy link
Member Author

@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.

@javiercn javiercn merged commit ab4d89f into main Jul 25, 2022
@javiercn javiercn deleted the javiercn/base-path branch July 25, 2022 14:03
@javiercn
Copy link
Member Author

/backport to release/6.0.4xx

TanayParikh pushed a commit that referenced this pull request Aug 11, 2022
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)
TanayParikh added a commit that referenced this pull request Aug 16, 2022
* [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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-AspNetCore RazorSDK, BlazorWebAssemblySDK, dotnet-watch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

HotReload files generated in a wrong path for MAUI Blazor projects
3 participants