Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Step by Step: Working with CRM2011 plugin profiler

Step by Step: Working with CRM2011 plugin profiler

View products that this article applies to.

About Author:

This article is provided by MVP Lo Toong Yang. Microsoft is so thankful that MVPs who proactively share their professional experience with other users. The article would be posted on MVP's website or blog later.

↑ Back to the top

Have you ever stuck in a situation where the plugin working perfectly in test environment but not the production environment?

Remote debugging might be a tricky setup in most of the production server because of the firewall constraint. We actually can debug the plugin without connecting to CRM server.

CRM2011 Plugin profiler provides the ability to capture user’s execution steps in the actual environment and replay it in plugin debugging mode.

↑ Back to the top

Prerequisite:

Download the latest CRM SDK from download center, compile the plugin registration tool solution inside.

SDK5.0.12

↑ Back to the top

More Information

Assumed we have a sample plugin code that will generate account number during the record creation step. We registered in CRM system and wish to debug with profiler using Visual studio.
Follow the steps below to step into Visual Studio breakpoint.
  1. From the plugin registration tool, click the
    Install Profiler.



  2. Once it finished, make sure
    Plugin Profiler exists.

  3. Select the plugin step needed to debug, click
    Profiler to enable profiling.

  4. Navigate to CRM system, perform the account creation which will trigger the plugin to be execute. Download the error log file and save in desktop.

  5. Run the visual studio solution, attach debug process named "PluginRegistration". Set a break point in the code.

  6. Open the plugin registration tool, click the Debug button.

  7. Browse the profile location with the erro log we downloaded in item 4. Choose the assembly location and click start plugin execution.

  8. System will auto step into visual studio breakpoint line.


↑ Back to the top



Community Solutions Content Disclaimer

MICROSOFT CORPORATION AND/OR ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY, RELIABILITY, OR ACCURACY OF THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN. ALL SUCH INFORMATION AND RELATED GRAPHICS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT AND/OR ITS RESPECTIVE SUPPLIERS HEREBY DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THIS INFORMATION AND RELATED GRAPHICS, INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, WORKMANLIKE EFFORT, TITLE AND NON-INFRINGEMENT. YOU SPECIFICALLY AGREE THAT IN NO EVENT SHALL MICROSOFT AND/OR ITS SUPPLIERS BE LIABLE FOR ANY DIRECT, INDIRECT, PUNITIVE, INCIDENTAL, SPECIAL, CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF USE, DATA OR PROFITS, ARISING OUT OF OR IN ANY WAY CONNECTED WITH THE USE OF OR INABILITY TO USE THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN, WHETHER BASED ON CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY OR OTHERWISE, EVEN IF MICROSOFT OR ANY OF ITS SUPPLIERS HAS BEEN ADVISED OF THE POSSIBILITY OF DAMAGES.

↑ Back to the top

Keywords: kb

↑ Back to the top

Article Info
Article ID : 2778280
Revision : 2
Created on : 9/2/2020
Published on : 9/2/2020
Exists online : False
Views : 207