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

Publish symbols for FluentUI assembly to Microsoft symbol servers #1607

Open
joperezr opened this issue Feb 28, 2024 · 4 comments
Open

Publish symbols for FluentUI assembly to Microsoft symbol servers #1607

joperezr opened this issue Feb 28, 2024 · 4 comments
Assignees
Labels
status:in-progress Work is in progress

Comments

@joperezr
Copy link
Member

Currently, it seems like the assemblies built out of this repository don't have their symbols pushed to Microsoft Symbol Servers. This is causing an issue since the dashboard for .NET Aspire uses some of the components in this repository, and given .NET Aspire ships as an optional component in Visual Studio, VS insertions are flagging issues due to assemblies in the drop not having their symbols published. Is this something that can be easily fixed?

@joperezr
Copy link
Member Author

cc: @vnbaaij

@vnbaaij vnbaaij self-assigned this Feb 28, 2024
@vnbaaij
Copy link
Collaborator

vnbaaij commented Feb 28, 2024

@joperezr I'm sure we can do that, but I will need some guidance from someone from the team. Ni idea what steps need to be taken for this.

@joperezr
Copy link
Member Author

Looks like this repo isn't using dotnet/arcade infrastructure for building, which would simplify symbol publishing as all of that comes for free with the infrastructure. @mmitche are you aware of any docs on how to onboard non-arcade repos but still owned by MSFT into symbol publishing to MSFT symbol servers?

@vnbaaij vnbaaij changed the title Publish symbols for FluientUI assembly to Microsoft symbol servers Publish symbols for FluentUI assembly to Microsoft symbol servers Feb 29, 2024
@vnbaaij vnbaaij added status:needs-investigation Needs additional investigation status:in-progress Work is in progress and removed status:needs-investigation Needs additional investigation labels Aug 20, 2024
@vnbaaij
Copy link
Collaborator

vnbaaij commented Aug 20, 2024

Task has been added to ADO pipeline. Need to check after run if everything worked as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:in-progress Work is in progress
Projects
None yet
Development

No branches or pull requests

2 participants