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

[wasm] Avoid unnecessary relinking when publishing a blazor project for AOT #82748

Merged
merged 11 commits into from
Mar 2, 2023

Commits on Mar 1, 2023

  1. Configuration menu
    Copy the full SHA
    b7e9946 View commit details
    Browse the repository at this point in the history
  2. cleanup

    radical committed Mar 1, 2023
    Configuration menu
    Copy the full SHA
    fcc38bb View commit details
    Browse the repository at this point in the history
  3. [wasm] Wasm.Build.Tests: Use $(_IsPublishing) to avoid unncessary

    .. relinking during "Build", when publishing.
    
    `Publish` target triggers `Build` target to run. When publishing, we
    don't want to run relinking step during the `Build`, as it will be run
    for `Publish` anyway. Earlier there wasn't a good way to differentiate
    the two cases of `build` when building, and `build` when publishing, but
    now the sdk sets `$(_IsPublishing)=true`, which can be used here.
    radical committed Mar 1, 2023
    Configuration menu
    Copy the full SHA
    4be35a7 View commit details
    Browse the repository at this point in the history
  4. fix blazor tests

    radical committed Mar 1, 2023
    Configuration menu
    Copy the full SHA
    306eb03 View commit details
    Browse the repository at this point in the history
  5. Wasm.Build.Tests: Add support for running published blazor projects

    `dotnet run` uses the regular build output. Published blazor app, like
    when using AOT, needs to be run more "manually" by starting a web server
    in the publish folder. This is accomplished here by using the new
    xharness command `wasm webserver`.
    radical committed Mar 1, 2023
    Configuration menu
    Copy the full SHA
    8950797 View commit details
    Browse the repository at this point in the history
  6. Configuration menu
    Copy the full SHA
    e5c4c0d View commit details
    Browse the repository at this point in the history
  7. Update test to track changes

    radical committed Mar 1, 2023
    Configuration menu
    Copy the full SHA
    5e7c968 View commit details
    Browse the repository at this point in the history
  8. cleanup

    radical committed Mar 1, 2023
    Configuration menu
    Copy the full SHA
    09052b6 View commit details
    Browse the repository at this point in the history
  9. Configuration menu
    Copy the full SHA
    17a8255 View commit details
    Browse the repository at this point in the history
  10. Update test to track changes

    radical committed Mar 1, 2023
    Configuration menu
    Copy the full SHA
    5ff3c1c View commit details
    Browse the repository at this point in the history

Commits on Mar 2, 2023

  1. Update xharness dependency

    Updating 'Microsoft.DotNet.XHarness.CLI': '1.0.0-prerelease.23117.1' => '1.0.0-prerelease.23151.1' (from build '20230301.1' of 'https://github.com/dotnet/xharness')
    Updating 'Microsoft.DotNet.XHarness.TestRunners.Common': '1.0.0-prerelease.23117.1' => '1.0.0-prerelease.23151.1' (from build '20230301.1' of 'https://github.com/dotnet/xharness')
    Updating 'Microsoft.DotNet.XHarness.TestRunners.Xunit': '1.0.0-prerelease.23117.1' => '1.0.0-prerelease.23151.1' (from build '20230301.1' of 'https://github.com/dotnet/xharness')
    radical committed Mar 2, 2023
    Configuration menu
    Copy the full SHA
    2ba2ac7 View commit details
    Browse the repository at this point in the history