web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :

Dynamics CRM Remote Debugging step by step

Zhongchen Zhou Profile Picture Zhongchen Zhou 681

1. Register and deploy the plug-in assembly.

2. Copy compiled plug-in assembly’s symbol file (.pdb) to the server’s <crm-root>\Server\bin\assembly folder and restart Internet Information Services (IIS)

3. If the plugin is a Sandboxed Plug-in, set the following registry key to 1 (DWORD) (Create one if it does not exist); restart “Microsoft Dynamics CRM Sandbox Processing Service” on the sandbox server

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM\SandboxDebugPlugins

 

4. Copy Remote Debugger (copy entire folder) from local visual studio install folder to remote server, it is located in

C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Remote Debugger\x64

5. Run msvsmon.exe you copied from previous step on remote server

6. Configure firewall for remote debugging on remote server

7. Copy remote debugger server name from Tools -> Options -> Server Name

8. Attach to process from local visual studio -> Debug -> Attach to process…

9. Set Transport to Default, set Qualifier to the value copies from step 7, (it might looks similar to this: Domain\Account@CRMServerName), select “Show processes from all users”

10. select the right process to attach depend on plug in

  • online: w3wp.exe
  • offline: Microsoft.Crm.Application.Hoster.exe
  • asynchronous registered plug-ins (or custom workflow assemblies): CrmAsyncService.exe
  • sandbox (isolation mode): Microsoft.Crm.Sandbox.WorkerProcess.exe

11. set one or more breakpoints in your plug-in code

12. trigger plugin to run


This was originally posted here.

Comments

*This post is locked for comments