Skip to content

Trim dotnet-watch and Microsoft.AspNetCore.Components.WebAssembly.DevServer package content #26448

Closed as not planned
Closed as not planned
Trim dotnet-watch and Microsoft.AspNetCore.Components.WebAssembly.DevServer package content#26448
Assignees
wtgodbe
Labels
Pillar: Technical Debtaffected-mostThis issue impacts most of the customersarea-blazorIncludes: Blazor, Razor ComponentsenhancementThis issue represents an ask for new feature or an enhancement to an existing onefeature-blazor-toolingBlazor specific tooling requestsfeature-blazor-wasmThis issue is related to and / or impacts Blazor WebAssemblyseverity-nice-to-haveThis label is used by an internal tool
Milestone
.NET 9 Planning

Description

@dougbu
dougbu
opened on Sep 30, 2020

The following image shows the content of the 5.0.0-rtm.20479.12 version of the Microsoft.AspNetCore.Components.WebAssembly.DevServer package. This includes shared framework assemblies such as Microsoft.Extensions.Configuration.Abstractions.dll. They're present because they're brought in transitively though Microsoft.AspNetCore.Components.WebAssembly.Server and published along with the content we really want.

image

Bottom line here is #24816 changes to Microsoft.AspNetCore.Components.WebAssembly.DevServer.csproj didn't have the expected outcome. Further I need to revert those changes in #24983 because they cause conflicts between 5.0 AspNetCore assemblies in the SDK and 6.0 assemblies Microsoft.AspNetCore.Components.WebAssembly.Server.csproj references. Need another way to either clean up the publish content or limit what ends up in the DevServer package.

Options include at least:

  1. List the exact files needed in the package in Microsoft.AspNetCore.Components.WebAssembly.DevServer.nuspec
  2. Muck w/ an item group like @(ReferenceCopyLocalPaths) to remove all @(ExternalAspNetCoreAppReference) items as well as aspnetcorev2_inprocess.dll in a well-timed target

Activity

  1. dougbu commented on Sep 30, 2020

    @dougbu
    dougbu
    on Sep 30, 2020
    ContributorAuthor

    Side note: @pranavkm and I have an open question about whether the package content is a bug worth fixing for 5.0.0 GA.

  2. dougbu
    added
    area-blazorIncludes: Blazor, Razor Components
    on Sep 30, 2020
  3. dougbu
    added a commit that references this issue on Sep 30, 2020

    Undo some of #24816

    da9a43e
  4. HaoK
    added this to the Backlog milestone on Sep 30, 2020
  6. SteveSandersonMS
    added
    affected-mostThis issue impacts most of the customers
    enhancementThis issue represents an ask for new feature or an enhancement to an existing one
    severity-nice-to-haveThis label is used by an internal tool
    on Oct 7, 2020
  7. dougbu
    added 2 commits that reference this issue on Oct 10, 2020

    Undo some of #24816

    22206a4

    Update branding to 6.0.0 Alpha1 (#24983)

    da7fead
  8. pranavkm
    changed the title [-]Trim Microsoft.AspNetCore.Components.WebAssembly.DevServer package content[/-] [+]Trim dotnet-watch and Microsoft.AspNetCore.Components.WebAssembly.DevServer package content[/+] on Oct 16, 2020
  9. javiercn
    added
    feature-blazor-wasmThis issue is related to and / or impacts Blazor WebAssembly
    feature-blazor-toolingBlazor specific tooling requests
    on Apr 20, 2021

  10. TanayParikh commented on Oct 19, 2021

    @TanayParikh
    TanayParikh
    on Oct 19, 2021
    Contributor

    @dougbu is this still an issue?

  11. pranavkm commented on Oct 19, 2021

    @pranavkm
    pranavkm
    on Oct 19, 2021
    Contributor

    Still an issue for the dev-server.

  12. 1 remaining item

  13. TanayParikh
    modified the milestones: .NET 7 Planning, Backlog on Oct 19, 2021
  15. mkArtakMSFT
    modified the milestones: Backlog, BlazorPlanning on Nov 5, 2023
  16. mkArtakMSFT
    added
    Pillar: Technical Debt
    on Nov 20, 2023

  17. mkArtakMSFT commented on Dec 14, 2023

    @mkArtakMSFT
    mkArtakMSFT
    on Dec 14, 2023
    Contributor

    @wtgodbe do you think you can handle this?

  18. mkArtakMSFT
    assigned
    wtgodbe
    on Dec 14, 2023
  19. mkArtakMSFT
    modified the milestones: Planning: WebUI, .NET 9 Planning on Dec 14, 2023

  21. wtgodbe commented on Dec 18, 2023

    @wtgodbe
    wtgodbe
    on Dec 18, 2023
    Member

    @wtgodbe do you think you can handle this?

    Sure thing, is it time critical?

  22. mkArtakMSFT commented on Jan 11, 2024

    @mkArtakMSFT
    mkArtakMSFT
    on Jan 11, 2024
    Contributor

    Closing as we've decided as this is not important.

  23. mkArtakMSFT
    closed this as not plannedon Jan 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Pillar: Technical Debtaffected-mostThis issue impacts most of the customersarea-blazorIncludes: Blazor, Razor ComponentsenhancementThis issue represents an ask for new feature or an enhancement to an existing onefeature-blazor-toolingBlazor specific tooling requestsfeature-blazor-wasmThis issue is related to and / or impacts Blazor WebAssemblyseverity-nice-to-haveThis label is used by an internal tool

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions