You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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
changed the title
Publish symbols for FluientUI assembly to Microsoft symbol servers
Publish symbols for FluentUI assembly to Microsoft symbol servers
Feb 29, 2024
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?
The text was updated successfully, but these errors were encountered: