Skip to content

Commit 95761e4

Browse files
author
Kraig Brockschmidt
authored
Merge pull request NuGet#675 from TripleEmcoder/master
Quick fix to provide more accurate SymbolSource information for now
2 parents 3ce7592 + 0db045c commit 95761e4

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/Create-Packages/Symbol-Packages.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,9 +17,9 @@ ms.reviewer:
1717

1818
# Creating symbol packages
1919

20-
In addition to building packages for nuget.org or other sources, NuGet also supports creating associated symbol packages and publishing them to the [SymbolSource repository](http://www.symbolsource.org/Public).
20+
In addition to building packages for nuget.org or other sources, NuGet also supports creating associated symbol packages and publishing them to the SymbolSource repository.
2121

22-
Package consumers can then add `http://srv.symbolsource.org/pdb/Public` to their symbol sources in Visual Studio, which allows stepping into package code in the Visual Studio debugger. See [Specify symbol (.pdb) and source files in the Visual Studio debugger](/visualstudio/debugger/specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger) for details on that process.
22+
Package consumers can then add `https://nuget.smbsrc.net` to their symbol sources in Visual Studio, which allows stepping into package code in the Visual Studio debugger. See [Specify symbol (.pdb) and source files in the Visual Studio debugger](/visualstudio/debugger/specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger) for details on that process.
2323

2424
## Creating a symbol package
2525

@@ -130,4 +130,4 @@ In this case, NuGet will publish `MyPackage.symbols.nupkg`, if present, to https
130130
131131
## See Also
132132
133-
[Using SymbolSource](https://www.symbolsource.org/Public/Wiki/Using) (symbolsource.org)
133+
[Moving to the new SymbolSource engine](https://tripleemcoder.com/2015/10/04/moving-to-the-new-symbolsource-engine/) (symbolsource.org)

0 commit comments

Comments
 (0)