This article discusses useful debugging tools when working with custom development within an Episerver site.
Below are some URL commands that can be used and the steps to configure this debug.
/<episerverUI>/Shell/Debug/InitializationModules
Lists out all registered registered initialisation modules.
/<episerverUI>/Shell/Debug/Menu
Lists out the menu items used to construct the top level menu.
/<episerverUI>/Shell/Debug/Routes
Lists out all routes in your RouteTable.
/<episerverUI>/Shell/Debug/ShellModules
Lists out all configured ShellModules.
/<episerverUI>/Shell/Debug/ShowFileVersions
Lists out the file versions used in your application (useful if you need to know exactly what assembly versions you have in your solutions).
/<episerverUI>/Shell/Debug/ShowTimeMeters
Lists out the initialisation modules and the time it takes to initialise each one.
/<episerverUI>/Shell/Debug/StructureMap
Lists all implementations in the underlying StructureMap container.
/<episerverUI>/Shell/Debug/ViewEngines
List out all registered view engines in your site.
To access the items above ensure the following are true:
1. The user accessing these tools is in the Administrators group
2. The following in the appSettings section of the web.config:
<configuration>
<appSettings>
<add key="EPi.DebugView.Enabled" value="true" />
</appSettings>
</configuration>
3. The <episerverUI> in the URL may be different for the site but in a default Episerver Alloy it is /Episerver/.
Please sign in to leave a comment.