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.

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

[release/6.0][wasm] Fix publishing *blazorwasm* project with lazy loaded assembly #60497

Closed
wants to merge 3 commits into from
Closed

[release/6.0][wasm] Fix publishing *blazorwasm* project with lazy loaded assembly #60497

wants to merge 3 commits into from

Commits on Oct 18, 2021

  1. [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.
    @radical
    radical committed Oct 18, 2021
    Configuration menu
    Copy the full SHA
    3bca81d View commit details
    Browse the repository at this point in the history

  2. bump sdk for workload testing to 6.0.100-rtm.21515.27

    @radical
    radical committed Oct 18, 2021
    Configuration menu
    Copy the full SHA
    75baa77 View commit details
    Browse the repository at this point in the history

  3. Revert BlazorOverwrite.targets

    @lewing
    lewing committed Oct 18, 2021
    Configuration menu
    Copy the full SHA
    8b0fdd8 View commit details
    Browse the repository at this point in the history