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
We are using the whole Azure DevOps suite and would like to use SourceLink for our internal NuGet packages.
Those packages are stored in Azure DevOps artifacts and the source code is stored in Azure DevOps Repos.
We build the packages with Azure DevOps pipelines.
There is no complete documentation on how to get this to work end to end and i have not been able to get it to work.
<PublishRepositoryUrl>true</PublishRepositoryUrl>
<!-- Optional: Embed source files that are not tracked by the source control manager in the PDB -->
<EmbedUntrackedSources>true</EmbedUntrackedSources>
<!-- Optional: Build symbol package (.snupkg) to distribute the PDB containing Source Link -->
<IncludeSymbols>true</IncludeSymbols>
<SymbolPackageFormat>snupkg</SymbolPackageFormat>
Embed PDBs into the nuget package as Artifacts does not support .snupkg files
Everthing else should happen automagically
Neither dotnet build (With GeneratePackageOnBuild=true) nor dotnet pack produce nuget packages with a set repository url.
Our current build step looks like this (With GeneratePackageOnBuild=true):
We are using the whole Azure DevOps suite and would like to use SourceLink for our internal NuGet packages.
Those packages are stored in Azure DevOps artifacts and the source code is stored in Azure DevOps Repos.
We build the packages with Azure DevOps pipelines.
There is no complete documentation on how to get this to work end to end and i have not been able to get it to work.
From what i have gathered so far:
.snupkg
filesNeither
dotnet build
(WithGeneratePackageOnBuild=true
) nordotnet pack
produce nuget packages with a set repository url.Our current build step looks like this (With GeneratePackageOnBuild=true):
What i have notices that packages build with Visual Studio produce nuget packages with valid source link information.
The text was updated successfully, but these errors were encountered: