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
If your project uses .NET SDK 8+ and is hosted by the above providers it does not need to reference any Source Link packages or set any build properties.
Otherwise, you can enable Source Link experience in your project by setting a few properties and adding a PackageReference to a Source Link package specific to the provider:
<Project>
<PropertyGroup>
<!-- Optional: Publish the repository URL in the built .nupkg (in the NuSpec <Repository> element) -->
<PublishRepositoryUrl>true</PublishRepositoryUrl>
<!-- Optional: Embed source files that are not tracked by the source control manager in the PDB -->
<EmbedUntrackedSources>true</EmbedUntrackedSources>
</PropertyGroup>
<ItemGroup>
<!-- Add PackageReference specific for your source control provider (see below) -->
</ItemGroup>
</Project>
Both NuGet Package Explorer and the binlog tell me that EmbedUntrackedSources is set automatically, but PublishRepositoryUrl is not. I do see that GenerateRepositoryUrlAttribute = true is set automatically.
Without explicit PublishRepositoryUrl:
With explicit PublishRepositoryUrl:
I guess this is simply a documentation error, and not a bug in the SDK?
The text was updated successfully, but these errors were encountered:
From the README:
Both NuGet Package Explorer and the binlog tell me that
EmbedUntrackedSources
is set automatically, butPublishRepositoryUrl
is not. I do see thatGenerateRepositoryUrlAttribute = true
is set automatically.Without explicit
![image](https://private-user-images.githubusercontent.com/1618054/303951782-cab83d07-4a2f-49c1-a621-7ecd4a7c522d.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjUzMzk4NzksIm5iZiI6MTcyNTMzOTU3OSwicGF0aCI6Ii8xNjE4MDU0LzMwMzk1MTc4Mi1jYWI4M2QwNy00YTJmLTQ5YzEtYTYyMS03ZWNkNGE3YzUyMmQucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDkwMyUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA5MDNUMDQ1OTM5WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ZGY0YzVkNGM2OGU3YTY0NDc0Zjg5ZTU2ZDBhMTg1ZmMwMGQ5ZDBjMGNlMzVhOTFmYTE0MjY0NDZlZTU4ZmIyOCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.ZqkY5MloWYwp_b0cILbMqyvhgu2SnCMgFjOfGY4w5hQ)
PublishRepositoryUrl
:With explicit
![image](https://private-user-images.githubusercontent.com/1618054/303951725-55eaddcc-cb3a-4ba7-99b6-7124c4b34f18.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjUzMzk4NzksIm5iZiI6MTcyNTMzOTU3OSwicGF0aCI6Ii8xNjE4MDU0LzMwMzk1MTcyNS01NWVhZGRjYy1jYjNhLTRiYTctOTliNi03MTI0YzRiMzRmMTgucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDkwMyUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA5MDNUMDQ1OTM5WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NmJmMTY1ZGRiMGU4MjIxZmRhMDEzYzU2NGE2ZjdkMWNjZTUzNDJiNDNiOWYxODkwN2ZjMmMzMTQ1YzFiMDU0ZSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.bTmNyNNUbPt6riW1wu_WizyhdV3E-KCgOJobyiOdw5Q)
PublishRepositoryUrl
:I guess this is simply a documentation error, and not a bug in the SDK?
The text was updated successfully, but these errors were encountered: