Login / Register  search  syndication  about

          Ryan Farley's Blog

Ryan Farley on .NET Development with a focus on CRM Development for SalesLogix

How to Debug a SalesLogix .NET Extension

The question of how to debug a .NET Extension has come up a few times in the SalesLogix Business Partner newsgroups as well as on the slxdeveloper.com forums. I've answered this a few times in those locations, so this might be a repeat of info for some, but I did think it was worthwhile to post again here as well.

Here's a step by step to debug your SalesLogix .NET Extension:

  1. Create your .NET Extension and compile it in debug mode
  2. Add it to the Extension Manager and add whatever scripts to launch it
  3. While the project is open in VS, go to "Debug" and then "Attach to Process".
  4. Find "SalesLogix" on the list of running processes. Select it and then use the "Select" button to ensure that you've chosen to debug "Managed".
  5. Set a break-point in VS in your code
  6. Run the script that uses the extension and it will stop at your break-point.

Have fun!

What's This?
  
Bookmark and Share

About Ryan Farley

   Ryan Farley is the Director of Development for Customer FX and creator of slxdeveloper.com. He's been blogging regularly about SalesLogix since 2001 and believes in sharing with the community. He loves C#, Javascript, Python, web development, open source, and Linux. He also loves his hobby as an amateur filmmaker.

View the SalesLogix Mobile Seveloper Series
View the SalesLogix SData Developer Series
View the Git for the SalesLogix Developer series



Related Content
   Confirming Actions With an "Are you sure?" Prompt in Infor CRM (Saleslogix)
I'm not a huge fan of bugging end users. I figure, if an end user clicked something, he or she meant
Posted on Nov 18, 2014 by Ryan Farley to Ryan Farley's Blog
 
   Delivering Data & Schema in SalesLogix Bundles
If you've had any exposure to SalesLogix, you'll have used a bundle. Bundles are great, but when
Posted on Apr 24, 2014 by Ryan Farley to Ryan Farley's Blog
 
   Using a Test Plan
So you have approved the Statement of Work (SOW) for some modifications and are awaiting the delivery of
Posted on Mar 13, 2014 by George Jensen to George Jensen's Blog
 
   Creating a Saleslogix Ticket Pretty Prefix and Suffix in External Applications
Some entities in SalesLogix, such as Tickets, use a "pretty key" as an easier to use value to r
Posted on Feb 28, 2014 by Ryan Farley to Ryan Farley's Blog
 
   Evaluating strings in C# Code snippets
When checking for two (or more) different values for a property in a code snippet, you can't simply l
Posted on Dec 13, 2013 by Jason Buss to Jason Buss' Blog
 
Comments

 

brads99 said:

I followed your steps, but I get the following message when I mouseover the breakpoint: "The breakpoint will not be currently hit.  No symbols have been loaded for this document."  

The .pdb file is in the \obj\debug directory along with the original .dll, but it appears that the debugger cannot see or load the debug symbols.

I'm trying to debug your "HelloWorld" plug-in.  By the way, the plug-in works perfectly and provides an excellent proof of concept to our team for a proposed integration project.

Thanks!

August 26, 2009 11:25 AM
 

brads99 said:

Solved my own probelm!  Once I actually clicked on the button in form that calls my plugin, the debugger stopped where it should have and all my breakpoints became active.

Thanks again!

August 26, 2009 11:32 AM
 

Unit Testing of .Net Extension in SalesLogix LAN « SRNR Blog said:

Pingback from  Unit Testing of .Net Extension in SalesLogix LAN «  SRNR Blog

February 1, 2012 5:19 PM

Leave a Comment

(required)  
(optional)
(required)  
Add
All contents Copyright © 2014 Customer FX Corporation
Customer FX Corporation
2324 University Avenue West, Suite 115
Saint Paul, Minnesota 55114
Tel: 800.728.5783

  Follow @CustomerFX on twitter
Follow the best news, tips, and articles
  Subscribe to Customer FX on youtube
Watch SalesLogix tutorial videos from Customer FX
Login / Register