Debug Server

Introduction

The Debug engine wraps around the Tridion DebugSession and uses the same template rendering process as the standard Tridion Template Builder application.

The Debug engine server exposes the created DebugSession through a locally hosted CompoundTemplateWebservice proxy.

This allows the user to connect using the default SDL Tridion Template Builder while still executing templates locally.

Details

When the template builder runs a template it connects to the CompoundTemplate webservice located at

http://<cmshost>/templating/compoundtemplatewebservice.asmx.

The locally hosted webservice is using Windows Communication Foundation self-hosting to provide an emulated compound template webservice proxy on the local machine.

Requests for Tridion data are forwarded to the configured Tridion host, however requests for debug session related information are captured and handled locally through a hosted RemoteDebugger in a seperate application domain.

The usage of a separate ApplicationDomain means that each DebugSession runs entirely isolated and ensures that no caching of pre-compiled assemblies occurs between different debugging sessions.

The Debug engine server itself makes use of the same concepts as detailed in Debug Engine.