Documentation Center

Debugging Content Manager

Debug Content Manager using the Visual Studio Debugger, attaching to the Windows process that is causing you problems.

Procedure

To debug Content Manager, use Visual Studio Debugger to attach to a running host process. Which host process to choose depends largely on the client you use, and on how that client communicates with SDL Tridion Sites. For example, to debug templating code, attach to TcmTemplateDebugHost when running Template Builder, or to TcmPublisher.exe when publishing. You can attach to the following processes:
W3WP.exe

You use this IIS Application Pool process if you connect to the Core Service through HTTP. This is the case for your custom HTTP clients connecting to the Core Service and for working with user preferences, favorites and (un)publishing in Content Manager Explorer. Any extensions for Content Manager Explorer you created are also hosted in W3WP.exe.

TcmBatchProcessor.exe
This process hosts batch invokers (an extension point)
TcmServiceHost.exe
You use this Windows Service process if you connect to the Core Service through net.tcp. This includes the use of Content Manager Explorer and Experience Manager.
TcmTemplateDebugHost.exe
Only the Template Builder client uses this process. Attach to it only when you debug templating code from Template Builder.
TcmPublisher.exe
Any functionality related to publishing uses this process. That is, to debug any Event Handler code that is triggered by an action related to publishing, as well as any template code executed during publishing, attach to TcmPublisher.exe
TcmWorkflowAgent.exe
This process hosts automated Workflow Activities.