Steps to Debug plug-in with profiler in CRM 2011

Steps to Debug plug-in with profiler in CRM 2011

Plug-in profiler is a very powerful debugging tool in CRM 2011. We can debug plug-ins with Plug-in profiler without connecting to CRM server or without remote debugging. By this, no need to re-deploy the plug-in to the Microsoft Dynamics CRM server until you have fixed the problem. Below are the steps to debug the plug-in with profiler: Connect to CRM using plugin registration tool. Click on Install Profiler You will find a new node attached to registered plugins “Plugin Profiler” Select a plug-in step and click Profile to enable profiling Start your plugin from MSCRM i.e. if your plugin is on Create, perform Create operation. After the plug-in throws an exception and the Business Process Error dialog is displayed, click Download Log File and save this file. Alternately, if the plug-in does not throw an exception, click Stop Profiling. In the Plug-in Registration tool, click Debug In the Debug Existing Plug-in dialog box, provide the location of the previously saved log file. In Step #2, specify the location of the plug-in assembly Launch Visual Studio 2010 and attach the debugger to the PluginRegistration.exe process. Set a breakpoint in the plug-in code. Click Start Plug-in Execution in the Debug Existing Plug-in dialog box. After a slight delay, the plug-in will execute using the same execution context that was passed to it by the Microsoft Dynamics CRM server and the debugger will stop execution on the breakpoint that you previously set. Continue debugging the plug-in as you would normally do. Any traces that the plug-in outputs are shown in the Debug Existing Plug-in dialog box. Note: The Plug-in Profiler is available in version 5.0.5 of the Microsoft Dynamics CRM SDK and later releases. Read more here on how to Analyze Plug-in Performance.