Testing and Debugging Rules Extensions

After you create a rules extension, you should test and, if necessary, debug it. Because rules extensions are run by the Forefront Identity Manager Synchronization Service (FIM Synchronization Service), testing and debugging is different than for a stand-alone application.

The following topics provide details about how to test and debug rules extensions:

• How to: Run an Extension In-Process and Out-of-Process

• Testing and Debugging

• How to: Attach the Visual Studio Debugger to the Process

• Setting Breakpoints

• Running Rules Extensions

• How to: View Contents of Variables

• Sending Text to the Debug Output Window

• How to: Set the Build Configuration

• Conditional Compilation Overview

• How to: Debug an Existing Extension

• How to: Catch Exceptions

• How to: Handle Exceptions

• Logging Extension Messages

Avoiding Synchronous Call Pitfalls

Synchronous calls can adversely affect the performance of synchronization processing. To avoid any performance issues, you should make calls to external processes or connected directories before or after running a management agent run profile.

See Also

Concepts

Using Forefront Identity Manager Synchronization Service
Using Rules Extensions
Using the WMI Provider