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

STAThreadAttribute is unnecessarily being left in a Blazor WASM default app #47861

Open
Tracked by #64603
eerhardt opened this issue Feb 4, 2021 · 8 comments
Open
Tracked by #64603

STAThreadAttribute is unnecessarily being left in a Blazor WASM default app #47861

eerhardt opened this issue Feb 4, 2021 · 8 comments
Labels
area-System.Runtime size-reduction Issues impacting final app size primary for size sensitive workloads
Milestone
Future

Comments

@eerhardt
Copy link
Member

eerhardt commented Feb 4, 2021

When publishing a Blazor WASM app, the STAThreadAttribute type is being left in the published app.

We should trim this attribute in a WASM app, as it doesn't serve a purpose.
@eerhardt eerhardt added area-System.Runtime size-reduction Issues impacting final app size primary for size sensitive workloads labels Feb 4, 2021
@ghost
Copy link

ghost commented Feb 4, 2021

Tagging subscribers to 'size-reduction': @eerhardt, @SamMonoRT, @marek-safar, @tannergooding
See info in area-owners.md if you want to be subscribed.

Issue Details

When publishing a Blazor WASM app, the STAThreadAttribute type is being left in the published app.

We should trim this attribute in a WASM app, as it doesn't serve a purpose.

Author: eerhardt
Assignees: tannergooding
Labels:

area-System.Runtime, size-reduction
Milestone: -

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Feb 4, 2021
@eerhardt eerhardt mentioned this issue Feb 4, 2021
Closed
17 tasks
@marek-safar
Copy link
Contributor

I think this is a subset of whole COM removal work #36659

@eerhardt
Copy link
Member Author

eerhardt commented Feb 4, 2021

We should be able to do this individually without doing the rest of the COM work.

@marek-safar
Copy link
Contributor

Sure, just saying this is not WASM specific but COM related so any e.g. Linux app could win

@SamMonoRT
Copy link
Member

@tannergooding - any update on this one - Is this going to be in for .NET6 ? Please update the milestone accordingly and remove the untriaged label.

@SamMonoRT SamMonoRT added this to the 6.0.0 milestone Jul 12, 2021
@SamMonoRT
Copy link
Member

@tannergooding - setting this for 6.0.0 - please update it.

@tannergooding tannergooding removed the untriaged New issue has not been triaged by the area owner label Jul 12, 2021
@SamMonoRT SamMonoRT modified the milestones: 6.0.0, 7.0.0 Jul 12, 2021
@SamMonoRT
Copy link
Member

Moving to 7.0.0

@jeffhandley jeffhandley mentioned this issue Feb 1, 2022
Closed
28 tasks
@tannergooding tannergooding removed their assignment Jun 12, 2022
@tannergooding
Copy link
Member

Unassigning myself, I had gotten pulled off this work to focus on Generic Math instead.

@jeffhandley jeffhandley modified the milestones: 7.0.0, Future Jul 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-System.Runtime size-reduction Issues impacting final app size primary for size sensitive workloads
Projects
None yet
Milestone
Future
Development

No branches or pull requests
5 participants
@marek-safar @jeffhandley @eerhardt @tannergooding @SamMonoRT