Setting up SymbolSource Server, a Screenshot Spectacular

Tuesday, August 07, 2012

Setting up SymbolSource Server, a Screenshot Spectacular

xavierdecoster.com - Setting up your own SymbolSource Server: step-by-step

"I’ve already explained why everyone should be using a symbols server. In that post, I explained that TFS comes with its own integrated symbols server, but at the moment it doesn’t play very nice with NuGet packages. Or maybe you are not using TFS at all.

That’s where SymbolSource comes in. NuGet has the ability to create symbols packages, so you can easily push them to a symbols package repository. This is exactly what SymbolSource offers, either as a public or private repository on SymbolSource.org, or as a separate cloud-based instance of SymbolSource where you also can manage users and repositories. Both plans are still in an unlimited free beta mode, so give it a try.

As much as I am a huge fan of the hosted SymbolSource offering, some people prefer to host code, symbols and packages on their own infrastructure, if only to troll some sys-admins or slow down development (if you’re a manager, I’m talking about security).

With the release of the SymbolSource community edition, I figured it was about time to try it out for myself.

...

..."

SymbolSource - Releasing the community edition of SymbolSource

For some time now we have been speaking about a community edition of SymbolSource. Starting from today it is available on NuGet the same way that NuGet.Server is, and serves a similar purpose: to internally host symbols and sources in a debugger-friendly way.

Setting it up your own symbol and source server

Installation of SymbolSource.Server.Basic is very simple:

Install Debugging Tools for Windows and note the installation path.

Create a new ASP.NET MVC 3 Web Application in Visual Studio.

Install the SymbolSource.Server.Basic package.

Fix <appSettings> in Web.config to point to your installation of Debugging Tools for Windows.

Run the application and start pushing symbol packages as usual.

If you point your browser to the application's start page, you'll see a list of all the needed URLs.

At this moment, the server accepts any NuGet API key, but you are free to secure it using any of the IIS authentication capabilities.

..."