ksjoberg
Apr 11, 2011
  10921
(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

Please login to comment.
Latest blogs
Follow-Up: Fixing JSON Casing in Optimizely CMS Export Data

A Targeted Action Filter to Enforce CamelCase In my previous blog post , I discussed an issue we were having with JSON formatting in Optimizely CMS...

KennyG | Jun 2, 2025

Going Headless: Optimizely Graph vs Content Delivery API

As the demand for flexible, multi-channel digital experiences grows, more development teams are turning to  headless CMS architectures to...

Michał Mitas | Jun 2, 2025

Opal vs Regular GenAI: A Deep Dive

Introduction For marketing teams grappling with inefficient content workflows and fragmented customer experiences, Generative AI (GenAI) offers a...

Patrick Lam | May 30, 2025

A day in the life of an Optimizely Developer - How Optimizely Opal AI transforms marketing operations with infinite scale

In May 2025, Optimizely revolutionized its AI capabilities with the next evolution of Opal, delivering what the company calls an "infinitely scalab...

Graham Carr | May 30, 2025

Adding granular editor access control to built-in parts of Optimizely CMS 12

A classic challenge in Optimizely CMS (well, really in any system I guess), is to ensure that the right people have the right access - and that...

Allan Thraen | May 30, 2025 |

Getting Started with CMS 12 and Commerce 14: A Beginner’s Guide to Creating CMS and Commerce Projects

Getting started with Optimizely can sometimes be confusing. I realized that a clear, step-by-step guide to creating a solution with separate CMS 12...

Julian | May 27, 2025