Skip to content

Commit b0006be

Browse files
committed
build task
1 parent 3e1b71d commit b0006be

File tree

3 files changed

+7
-4
lines changed

3 files changed

+7
-4
lines changed
Loading
Binary file not shown.

docs/artifacts/symbols/setting-up-github-sourcelinking.md

+7-4
Original file line numberDiff line numberDiff line change
@@ -20,15 +20,18 @@ When building .NET code in Azure DevOps Services the _Index and Publish Symbols_
2020
For source code that is hosted in Azure DevOps Services, that is all you need to do. However, for source code that is hosted on GitHub and being built in Azure DevOps Services you need to do a few extra steps.
2121

2222
> [!NOTE]
23-
> In order to publish symbols to and download symbols from the Azure DevOps Services Symbol Server you must have the [Azure Artifacts](https://marketplace.visualstudio.com/items?itemName=ms.feed) extension installed.
23+
> In order to publish symbols to and download symbols from the Azure DevOps Services Symbol Server you must have the [Azure Artifacts](https://marketplace.visualstudio.com/items?itemName=ms.feed) extension installed.
2424
2525
## Installing the Source Link Package
26-
Azure DevOps Services doesn't natively know how to map source code that originated from a GitHub repository so we need to give it a bit of a hand. To do that you need to install the ```SourceLink.Create.CommandLine``` package into your solution. This injects the logic necessary to map source code hosted in GitHub to symbols stored in PDB files so that the Visual Studio debugger can seamlessly download source files as another developer steps through your code.
26+
27+
Azure DevOps Services doesn't natively know how to map source code that originated from a GitHub repository so we need to give it a bit of a hand. To do that you need to install the `SourceLink.Create.CommandLine` package into your solution. This injects the logic necessary to map source code hosted in GitHub to symbols stored in PDB files so that the Visual Studio debugger can seamlessly download source files as another developer steps through your code.
2728

2829
## Modifying the Build Pipeline
29-
The next step is to modify the build pipeline to invoke Source Link. This is done by adding a ```/p:SourceLinkCreate=true``` parameter to the _MSBuild_ task.
3030

31-
![SourceLinkCreate property added to MSBuild arguments](media/msbuildsourcelinkcreateproperty.png)
31+
The next step is to modify the build pipeline to invoke Source Link. This is done by adding a `/p:SourceLinkCreate=true` parameter to the _MSBuild_ task.
32+
33+
> [!div class="mx-imgBorder"]
34+
> ![MSBuild arguments in the build solution task](media/build-solution-task-classic.png)
3235
3336
Once this is done you can save and queue the build pipeline and the GitHub source linking information will be embedded into the PDBs prior to be publishing to the symbol server in Azure DevOps Services.
3437

0 commit comments

Comments
 (0)