Skip to content

Investigate fully trimming assemblies used in Blazor-wasm #27730

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
Closed
CoffeeFlux opened this issue Nov 11, 2020 · 4 comments
Closed

Investigate fully trimming assemblies used in Blazor-wasm #27730

CoffeeFlux opened this issue Nov 11, 2020 · 4 comments
Labels
affected-most This issue impacts most of the customers area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one severity-minor This label is used by an internal tool
Milestone
6.0-preview4

Comments

@CoffeeFlux
Copy link

Because of concerns around functionality and interop, the aspnetcore libraries are not fully trimmed. We should investigate doing so for the ones used in Blazor-wasm to see what kind of size savings this could produce and how much work it would be to enable.
@CoffeeFlux CoffeeFlux mentioned this issue Nov 11, 2020
Closed
17 tasks
@pranavkm pranavkm added the area-blazor Includes: Blazor, Razor Components label Nov 11, 2020
@mkArtakMSFT
Copy link
Contributor

This is a dupe of #27384

@mkArtakMSFT mkArtakMSFT added the ✔️ Resolution: Duplicate Resolved as a duplicate of another issue label Nov 16, 2020
@ghost ghost added the Status: Resolved label Nov 16, 2020
@mkArtakMSFT
Copy link
Contributor

Reopening to track blazor-specific work as part of this.

@mkArtakMSFT mkArtakMSFT reopened this Dec 3, 2020
@mkArtakMSFT mkArtakMSFT added enhancement This issue represents an ask for new feature or an enhancement to an existing one and removed ✔️ Resolution: Duplicate Resolved as a duplicate of another issue Status: Resolved labels Dec 3, 2020
@mkArtakMSFT mkArtakMSFT added this to the 6.0-preview1 milestone Dec 3, 2020
@ghost
Copy link

ghost commented Jan 26, 2021

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

@SteveSandersonMS SteveSandersonMS added affected-most This issue impacts most of the customers severity-minor This label is used by an internal tool labels Jan 26, 2021 — with ASP.NET Core Issue Ranking
@pranavkm
Copy link
Contributor

All Blazor WASM assemblies have been annotated with trimmer attributes and marked as IsTrimmable=true as of preview4.

@ghost ghost locked as resolved and limited conversation to collaborators Apr 24, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
affected-most This issue impacts most of the customers area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one severity-minor This label is used by an internal tool
Projects
None yet
Milestone
6.0-preview4
Development

No branches or pull requests
4 participants
@pranavkm @SteveSandersonMS @CoffeeFlux @mkArtakMSFT