ksjoberg
Apr 11, 2011
visibility 11555
star star star star star
(4 votes)

Symbols published for products in the R2 wave 2011

The debugging symbols for the second release of EPiServer CMS, Community, Mail, Composer and Commerce have now been published on http://symbols.episerver.com/.

Let me show you how to set up a few common debuggers to automatically download symbols from our store.

Visual Studio 2008/2010

Open up the Tools menu, and select Options… In the dialog that appears, open “Debugging” and select Symbols. Here, enter our symbol server location and a local directory for the symbol cache.

image

With the symbols, the Call Stack window now displays a little bit more information:

image

How to download the symbols for a set of EPiServer DLLs

With the symchk.exe tool, which is a part of Debugging Tools for Windows, you may obtain the symbols for a set of DLLs on your local machine. This is how you can download the EPiServer symbols for a web application.

  1. Make sure you have Debugging Tools for Windows installed
  2. Open up a command prompt in the directory that contain the EPiServer DLLs whose symbols you want to obtain.
  3. Run the command "\Program Files\Debugging Tools for Windows (x86)\symchk.exe" *.dll /s SRV*http://symbols.episerver.com/ /oc .
    You may need to adjust the path to the symchk.exe tool depending on your CPU architecture.

The parameter “*.dll” specifies that symbols for all DLLs in the current directory should be requested from the symbol server. The next parameter, /s SRV*http://symbols.episerver.com/, specifies which symbol path to use. The last parameter, /oc . tells the symchk.exe tool to output all the downloaded symbols to the current directory (alongside the DLLs).

A typical AlloyTech bin folder looks like this just after the installation:

image

Using the symchk.exe tool, the symbols are downloaded from EPiServer’s symbol server to the current folder.

image

After the command has finished executing, the bin folder of the site have been populated with PDBs for all binaries that matched a symbol on our symbol server.

image

Configuring WinDBG

Usually, you configure WinDBG’s symbol search path to include Microsoft’s Symbol Server. You may add EPiServer’s symbol store too, and search it as well as Microsoft’s symbol store. Just include SRV*C:\Symbols*http://symbols.episerver.com/ in the Symbol Search Path. Separate multiple entries with semi-colon.

image

Happy debugging!

Apr 11, 2011

Comments

error Please login to comment.
Latest blogs
Copies vs. Connections: Modeling Content Areas for Multilingual Success

Starting With the Simple Question Most multilingual content modeling conversations start with a deceptively simple question from a client: "If we s...

Vipin Banka | Aug 23, 2026

Content Transfer coming to Optimizely SaaS CMS

Back in June I released Content Transfer on the Optimizely nuget feed – today I’m releasing version 1.0 , because we’ve had it running out in the...

Matt Pallatt | Aug 23, 2026

Improving Optimizely Product Information in LLM Tools

Tools like Claude Code can be great for working with Optimizely CMS, but when they index outdated or incomplete information about developing a...

Nicholas Sideras | Aug 21, 2026 |

How to Get a Bacpac Out of DXP (And Never Do It By Hand Again)

Every Optimizely DXP project eventually runs into the same task: getting production data onto a local machine so you can actually troubleshoot...

KennyG | Aug 20, 2026