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 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:
TcmBatchProcessor.exe
The Batch Processer Windows process, which hosts batch invokers (an extension point).
TcmPublisher.exe
The Publisher Windows process for various (but not all) publishing functionality.
Attach to this process to debug any Event Handler code that is triggered by an action related to publishing, as well as any template code executed during publishing.
TcmServiceHost.exe
The Service Host Windows process, which you can use to connect to the Core Service through net.tcp. (This includes the use of Content Manager Explorer and Experience Manager.)
TcmTemplateDebugHost.exe
The Template Builder client process, which you can attach to if you need to debug templating code from Template Builder.
TcmWorkflowAgent.exe
This Workflow Agent process, which hosts automated Workflow Activities.
W3WP.exe
The IIS Worker Process that you can use to connect to the Core Service or Core Service.REST API through HTTP.
Use W3WP.exe for custom HTTP clients connecting to the APIs and for working with user preferences, favorites, publishing and unpublishing from the Content Manager user interfaces. In addition, any extensions you have created for Content Manager Explorer are also hosted in W3WP.exe.