crmplugin Release Rss Feed

UPDATED RELEASE: Plugin Registration Tool 2.2 (Jan 02, 2009)

Fri, 12 Jun 2009 18:16:40 GMT

!! Jun 2009
Updated the PluginRegistration.exe so that it no longer complains about the Load Assembly error. (I had to rename this to Pluginregistration.exe) and Fixed V3 Callouts to show "Upgraded Callout"

!! Updates in Ver 2.2
* *Support for +Scripting+ for Import /Export operation in the tool*
PluginDeveloper tool shipped in the SDK has the console application support for scripting but i have got many requests to add support for scripting in the PlguinRegistration tool so that they could use it for deployment purposes.
PluginRegistration Tool assumes that you have secure trust established to the CRM server so it doesn't ask for the credentials. If you do want to run the tool across domains, then you can save the credentials of the CRM server in the Windows->Stored User Names repository and run the application.

Usage as follows:
/c:<connectionFileName> /cl:<connectionLabel> /org:<organizationName> /op:<operation> /f:<importExportFilename> /n:<ignoreGuids>
Parameter information:
<connectionFileName> name of the connections file, default: Connections.config
<connectionLabel>* name of the connection label in the connections config file, Example: newconnection
<organizationName> name of the working organization, Required in a multi-org deployment, defaults to the single org in a single org deployment
<operation>* name of the operation, valid entries: import, export
<operationFilename>* name of file you want to export or import, Example: import.xml
<ignoreGuids> boolean value (true or false), ignore guids if you are re-importing a group of plugins/workflows
* denotes requried attributes
All the assemblies need to be imported should be in the same folder as the executing exe and so the export.xml file
/? Show this help

* *Fixed the OutofMemoryException problem when trying to registering a step on an Imported Organization.*
* *Fixed the bug in Image registration wizard (Minimum value cannot be greater than maximum value)*
* *Fixed the bug when updating the Impersonation on Step from specified user to "Current User"*

Please provide you feedback using comments / Discussions /Issue Tracker.

Thanks
-Ajithg

UPDATED RELEASE: Plugin Registration Tool 2.2 (Jan 02, 2009)

Fri, 12 Jun 2009 18:15:24 GMT

UPDATED RELEASE: Plugin Registration Tool 2.2 (Jan 02, 2009)

Wed, 08 Apr 2009 19:29:59 GMT

!! April 2009
Updated the PluginRegistration.exe so that it no longer complains about the Load Assembly error. (I had to rename this to Pluginregistration.exe)

!! Updates in Ver 2.2
* *Support for +Scripting+ for Import /Export operation in the tool*
PluginDeveloper tool shipped in the SDK has the console application support for scripting but i have got many requests to add support for scripting in the PlguinRegistration tool so that they could use it for deployment purposes.
PluginRegistration Tool assumes that you have secure trust established to the CRM server so it doesn't ask for the credentials. If you do want to run the tool across domains, then you can save the credentials of the CRM server in the Windows->Stored User Names repository and run the application.

Usage as follows:
/c:<connectionFileName> /cl:<connectionLabel> /org:<organizationName> /op:<operation> /f:<importExportFilename> /n:<ignoreGuids>
Parameter information:
<connectionFileName> name of the connections file, default: Connections.config
<connectionLabel>* name of the connection label in the connections config file, Example: newconnection
<organizationName> name of the working organization, Required in a multi-org deployment, defaults to the single org in a single org deployment
<operation>* name of the operation, valid entries: import, export
<operationFilename>* name of file you want to export or import, Example: import.xml
<ignoreGuids> boolean value (true or false), ignore guids if you are re-importing a group of plugins/workflows
* denotes requried attributes
All the assemblies need to be imported should be in the same folder as the executing exe and so the export.xml file
/? Show this help

* *Fixed the OutofMemoryException problem when trying to registering a step on an Imported Organization.*
* *Fixed the bug in Image registration wizard (Minimum value cannot be greater than maximum value)*
* *Fixed the bug when updating the Impersonation on Step from specified user to "Current User"*

Please provide you feedback using comments / Discussions /Issue Tracker.

Thanks
-Ajithg

UPDATED RELEASE: Plugin Registration Tool 2.2 (Jan 02, 2009)

Wed, 08 Apr 2009 19:29:32 GMT

April 2009
Updated the PluginRegistration.exe so that it no longer complains about the Load Assembly error. (I had to rename this to Pluginregistration.exe)

!! Updates in Ver 2.2
* *Support for +Scripting+ for Import /Export operation in the tool*
PluginDeveloper tool shipped in the SDK has the console application support for scripting but i have got many requests to add support for scripting in the PlguinRegistration tool so that they could use it for deployment purposes.
PluginRegistration Tool assumes that you have secure trust established to the CRM server so it doesn't ask for the credentials. If you do want to run the tool across domains, then you can save the credentials of the CRM server in the Windows->Stored User Names repository and run the application.

Usage as follows:
/c:<connectionFileName> /cl:<connectionLabel> /org:<organizationName> /op:<operation> /f:<importExportFilename> /n:<ignoreGuids>
Parameter information:
<connectionFileName> name of the connections file, default: Connections.config
<connectionLabel>* name of the connection label in the connections config file, Example: newconnection
<organizationName> name of the working organization, Required in a multi-org deployment, defaults to the single org in a single org deployment
<operation>* name of the operation, valid entries: import, export
<operationFilename>* name of file you want to export or import, Example: import.xml
<ignoreGuids> boolean value (true or false), ignore guids if you are re-importing a group of plugins/workflows
* denotes requried attributes
All the assemblies need to be imported should be in the same folder as the executing exe and so the export.xml file
/? Show this help

* *Fixed the OutofMemoryException problem when trying to registering a step on an Imported Organization.*
* *Fixed the bug in Image registration wizard (Minimum value cannot be greater than maximum value)*
* *Fixed the bug when updating the Impersonation on Step from specified user to "Current User"*

Please provide you feedback using comments / Discussions /Issue Tracker.

Thanks
-Ajithg

UPDATED RELEASE: Plugin Registration Tool 2.2 (Jan 02, 2009)

Wed, 08 Apr 2009 19:28:06 GMT

!! Updates in Ver 2.2
* *Support for +Scripting+ for Import /Export operation in the tool*
PluginDeveloper tool shipped in the SDK has the console application support for scripting but i have got many requests to add support for scripting in the PlguinRegistration tool so that they could use it for deployment purposes.
PluginRegistration Tool assumes that you have secure trust established to the CRM server so it doesn't ask for the credentials. If you do want to run the tool across domains, then you can save the credentials of the CRM server in the Windows->Stored User Names repository and run the application.

Usage as follows:
/c:<connectionFileName> /cl:<connectionLabel> /org:<organizationName> /op:<operation> /f:<importExportFilename> /n:<ignoreGuids>
Parameter information:
<connectionFileName> name of the connections file, default: Connections.config
<connectionLabel>* name of the connection label in the connections config file, Example: newconnection
<organizationName> name of the working organization, Required in a multi-org deployment, defaults to the single org in a single org deployment
<operation>* name of the operation, valid entries: import, export
<operationFilename>* name of file you want to export or import, Example: import.xml
<ignoreGuids> boolean value (true or false), ignore guids if you are re-importing a group of plugins/workflows
* denotes requried attributes
All the assemblies need to be imported should be in the same folder as the executing exe and so the export.xml file
/? Show this help

* *Fixed the OutofMemoryException problem when trying to registering a step on an Imported Organization.*
* *Fixed the bug in Image registration wizard (Minimum value cannot be greater than maximum value)*
* *Fixed the bug when updating the Impersonation on Step from specified user to "Current User"*

Please provide you feedback using comments / Discussions /Issue Tracker.

Thanks
-Ajithg

UPDATED RELEASE: Plugin Registration Tool 2.2 (Jan 02, 2009)

Mon, 16 Mar 2009 21:39:40 GMT

UPDATED RELEASE: Plugin Registration Tool 2.2 (Jan 02, 2009)

Fri, 23 Jan 2009 02:30:50 GMT

UPDATED RELEASE: Plugin Registration Tool 2.2 (Jan 02, 2009)

Thu, 15 Jan 2009 23:16:40 GMT

CREATED RELEASE: Plugin Registration Tool 2.2 (Jan 02, 2009)

Sat, 03 Jan 2009 03:56:57 GMT

UPDATED RELEASE: Plugin Registration Tool 2.1 (Jun 20, 2008)

Fri, 07 Nov 2008 06:54:21 GMT

!! Updated on Nov 6
- Increased the Crm Connections timeout to infinite time instead of 60 sec.
- Uploaded the Exe so you dont have to rebuild the tool
- Project upgraded to VS 2008

!! Here are the new additions to Ver 2.1. (Jun 20)
*Works with https:// or SSL based Installs. (SDK calls)*
- I Accept all Server Certificates. If you need to change the code look in the CrmConnection.myCertificateValidation implementation
*Shows the Endpoints returned by the Discovery service before making call to CrmService SDK*
- This allows you to change the endpoint from the client if Discovery service information is not correct for registering plugins. This usually is needed for IFD or for troubleshooting purposes
*Images for Parent and Subordinate entitities for Merge request*
- Now you can register an Image for Subordinate entity also for Merge request. You shall get a pop-up that asks if you need to register for Subordinate or parent

# Works on IFD only if logged on the Deployment server using AD auth
# Import Solution honors ImageType in the xml
# Works with *Visual Studio 2008*
# Restricts registering PreImage for PreCreate

!! Sceanrios
* *Developer Scenario:* An ISV creates a plug-in and registers it on Contact Create as PreCallout (Aka BeforeMainOperation Plug-in). He can then debug the plug-in by registering on Disk. Once the errors are fixed, he can then update the pluginassembly to be uploaded to the database.
* *Deployment Scenario:* An ISV builds few plug-ins and registers on multiples steps. Images are registered on few of them. He tests them in the Dev environment but would like to port the registrations to a different organization. PluginRegistration tool supports Export and Import of the solution xml to solve this scenario.
* *Admin Console:* Couple of ISV installs their plug-ins on a Customer Organization. Admin at the Customer side saw some problems with “Contact Create” action. He would like to know what plug-in are fired and what the pipeline is for the “Contact – Create”. He then finds the trouble causing plug-in and disables it. So it is all about troubleshooting. PluginRegistration tool solves this problem by allowing Enable/Disable/Unregister operations on steps, plug-in.

!! Complete feature-set of the tool
# Register a pluginassembly, step and image. Validates the data before sending to CRM
# Update pluginassembly, step and image
# Unregister a pluginassembly shall cascade unregister all the children
# Enable, Disable a step
# Auto retrieve all CustomEntities information from the organization when registering the step
# Allows setting more values on step (e.g.: configuration, secureconfiguration, filteringattributes, etc.)
# Auto retrieve CustomAttributes on entity when registering images
# Search the pluginassembly, type, steps, images by names
# Visualize the status of the CRM Organization multiple views
## View by Assembly : What steps are registered on what plug-in
## View by Entity : What steps are registered on an entity(e.g.: contact)
## View by Message : What steps are registered on a message (e.g.: create)
# Shows the list of Microsoft Dynamics CRM 3.0 callouts registered in the organization
# Work with multiple organizations at the same time
# Exports the Xml in the same format that can be accepted by PluginDeveloper tool

UPDATED RELEASE: Plugin Registration Tool 2.1 (Jun 20, 2008)

Fri, 07 Nov 2008 06:51:45 GMT

!! Here are the new additions to Ver 2.1. (Jun 20)
*Works with https:// or SSL based Installs. (SDK calls)*
- I Accept all Server Certificates. If you need to change the code look in the CrmConnection.myCertificateValidation implementation
*Shows the Endpoints returned by the Discovery service before making call to CrmService SDK*
- This allows you to change the endpoint from the client if Discovery service information is not correct for registering plugins. This usually is needed for IFD or for troubleshooting purposes
*Images for Parent and Subordinate entitities for Merge request*
- Now you can register an Image for Subordinate entity also for Merge request. You shall get a pop-up that asks if you need to register for Subordinate or parent

# Works on IFD only if logged on the Deployment server using AD auth
# Import Solution honors ImageType in the xml
# Works with *Visual Studio 2008*
# Restricts registering PreImage for PreCreate

!! Sceanrios
* *Developer Scenario:* An ISV creates a plug-in and registers it on Contact Create as PreCallout (Aka BeforeMainOperation Plug-in). He can then debug the plug-in by registering on Disk. Once the errors are fixed, he can then update the pluginassembly to be uploaded to the database.
* *Deployment Scenario:* An ISV builds few plug-ins and registers on multiples steps. Images are registered on few of them. He tests them in the Dev environment but would like to port the registrations to a different organization. PluginRegistration tool supports Export and Import of the solution xml to solve this scenario.
* *Admin Console:* Couple of ISV installs their plug-ins on a Customer Organization. Admin at the Customer side saw some problems with “Contact Create” action. He would like to know what plug-in are fired and what the pipeline is for the “Contact – Create”. He then finds the trouble causing plug-in and disables it. So it is all about troubleshooting. PluginRegistration tool solves this problem by allowing Enable/Disable/Unregister operations on steps, plug-in.

!! Complete feature-set of the tool
# Register a pluginassembly, step and image. Validates the data before sending to CRM
# Update pluginassembly, step and image
# Unregister a pluginassembly shall cascade unregister all the children
# Enable, Disable a step
# Auto retrieve all CustomEntities information from the organization when registering the step
# Allows setting more values on step (e.g.: configuration, secureconfiguration, filteringattributes, etc.)
# Auto retrieve CustomAttributes on entity when registering images
# Search the pluginassembly, type, steps, images by names
# Visualize the status of the CRM Organization multiple views
## View by Assembly : What steps are registered on what plug-in
## View by Entity : What steps are registered on an entity(e.g.: contact)
## View by Message : What steps are registered on a message (e.g.: create)
# Shows the list of Microsoft Dynamics CRM 3.0 callouts registered in the organization
# Work with multiple organizations at the same time
# Exports the Xml in the same format that can be accepted by PluginDeveloper tool

UPDATED RELEASE: Plugin Registration Tool 2.1 (Jun 20, 2008)

Fri, 07 Nov 2008 06:49:23 GMT

UPDATED RELEASE: Plugin Registration Tool 2.1 (Jun 20, 2008)

Fri, 07 Nov 2008 06:48:33 GMT

UPDATED RELEASE: Plugin Registration Tool 2.1 (Jun 20, 2008)

Mon, 11 Aug 2008 23:04:12 GMT

UPDATED RELEASE: Plugin Registration Tool 2.0 (Bug Fixes) (May 05, 2008)

Fri, 20 Jun 2008 22:35:40 GMT

!! Alert: I see people downloading from both releases, so i updated the original release with all the latest code.

I have fixed couple of bugs in the tool. It is now in sync with the *Microsoft CRM SDk 4.0* release. If there are any major changes I would update the code, else it is going to be the same. (No major work is planned !!!).

# Works on IFD only if logged on the Deployment server using AD auth
# Import Solution honors ImageType in the xml
# Works with *Visual Studio 2008*
# Restricts registering PreImage for PreCreate

Thanks
AjithG

UPDATED RELEASE: Plugin Registration Tool 2.1 (Jun 20, 2008)

Fri, 20 Jun 2008 22:13:25 GMT

!! Made this the Current release for all downlaods as i see more tarffic on this link than other release tabs
!! Here are the new additions to Ver 2.1. (Jun 20)
*Works with https:// or SSL based Installs. (SDK calls)*
- I Accept all Server Certificates. If you need to change the code look in the CrmConnection.myCertificateValidation implementation
*Shows the Endpoints returned by the Discovery service before making call to CrmService SDK*
- This allows you to change the endpoint from the client if Discovery service information is not correct for registering plugins. This usually is needed for IFD or for troubleshooting purposes
*Images for Parent and Subordinate entitities for Merge request*
- Now you can register an Image for Subordinate entity also for Merge request. You shall get a pop-up that asks if you need to register for Subordinate or parent

# Works on IFD only if logged on the Deployment server using AD auth
# Import Solution honors ImageType in the xml
# Works with *Visual Studio 2008*
# Restricts registering PreImage for PreCreate

!! Sceanrios
* *Developer Scenario:* An ISV creates a plug-in and registers it on Contact Create as PreCallout (Aka BeforeMainOperation Plug-in). He can then debug the plug-in by registering on Disk. Once the errors are fixed, he can then update the pluginassembly to be uploaded to the database.
* *Deployment Scenario:* An ISV builds few plug-ins and registers on multiples steps. Images are registered on few of them. He tests them in the Dev environment but would like to port the registrations to a different organization. PluginRegistration tool supports Export and Import of the solution xml to solve this scenario.
* *Admin Console:* Couple of ISV installs their plug-ins on a Customer Organization. Admin at the Customer side saw some problems with “Contact Create” action. He would like to know what plug-in are fired and what the pipeline is for the “Contact – Create”. He then finds the trouble causing plug-in and disables it. So it is all about troubleshooting. PluginRegistration tool solves this problem by allowing Enable/Disable/Unregister operations on steps, plug-in.

!! Complete feature-set of the tool
# Register a pluginassembly, step and image. Validates the data before sending to CRM
# Update pluginassembly, step and image
# Unregister a pluginassembly shall cascade unregister all the children
# Enable, Disable a step
# Auto retrieve all CustomEntities information from the organization when registering the step
# Allows setting more values on step (e.g.: configuration, secureconfiguration, filteringattributes, etc.)
# Auto retrieve CustomAttributes on entity when registering images
# Search the pluginassembly, type, steps, images by names
# Visualize the status of the CRM Organization multiple views
## View by Assembly : What steps are registered on what plug-in
## View by Entity : What steps are registered on an entity(e.g.: contact)
## View by Message : What steps are registered on a message (e.g.: create)
# Shows the list of Microsoft Dynamics CRM 3.0 callouts registered in the organization
# Work with multiple organizations at the same time
# Exports the Xml in the same format that can be accepted by PluginDeveloper tool

UPDATED RELEASE: Plugin Registration Tool 2.1 (Feb 01, 2008)

Fri, 20 Jun 2008 22:07:42 GMT

!! Made this the Current release for all downlaods as i see more tarffic on this link than other release tabs
!! Here are the new additions to Ver 2.1. (Jun 20)
*Works with https:// or SSL based Installs. (SDK calls)*
- I Accept all Server Certificates. If you need to change the code look in the CrmConnection.myCertificateValidation implementation
*Shows the Endpoints returned by the Discovery service before making call to CrmService SDK*
- This allows you to change the endpoint from the client if Discovery service information is not correct for registering plugins. This usually is needed for IFD or for troubleshooting purposes
*Images for Parent and Subordinate entitities for Merge request*
- Now you can register an Image for Subordinate entity also for Merge request. You shall get a pop-up that asks if you need to register for Subordinate or parent

!! Sceanrios
* *Developer Scenario:* An ISV creates a plug-in and registers it on Contact Create as PreCallout (Aka BeforeMainOperation Plug-in). He can then debug the plug-in by registering on Disk. Once the errors are fixed, he can then update the pluginassembly to be uploaded to the database.
* *Deployment Scenario:* An ISV builds few plug-ins and registers on multiples steps. Images are registered on few of them. He tests them in the Dev environment but would like to port the registrations to a different organization. PluginRegistration tool supports Export and Import of the solution xml to solve this scenario.
* *Admin Console:* Couple of ISV installs their plug-ins on a Customer Organization. Admin at the Customer side saw some problems with “Contact Create” action. He would like to know what plug-in are fired and what the pipeline is for the “Contact – Create”. He then finds the trouble causing plug-in and disables it. So it is all about troubleshooting. PluginRegistration tool solves this problem by allowing Enable/Disable/Unregister operations on steps, plug-in.

!! Complete feature-set of the tool
# Register a pluginassembly, step and image. Validates the data before sending to CRM
# Update pluginassembly, step and image
# Unregister a pluginassembly shall cascade unregister all the children
# Enable, Disable a step
# Auto retrieve all CustomEntities information from the organization when registering the step
# Allows setting more values on step (e.g.: configuration, secureconfiguration, filteringattributes, etc.)
# Auto retrieve CustomAttributes on entity when registering images
# Search the pluginassembly, type, steps, images by names
# Visualize the status of the CRM Organization multiple views
## View by Assembly : What steps are registered on what plug-in
## View by Entity : What steps are registered on an entity(e.g.: contact)
## View by Message : What steps are registered on a message (e.g.: create)
# Shows the list of Microsoft Dynamics CRM 3.0 callouts registered in the organization
# Work with multiple organizations at the same time
# Exports the Xml in the same format that can be accepted by PluginDeveloper tool

UPDATED RELEASE: Plugin Registration Tool 2.0 (Feb 01, 2008)

Fri, 20 Jun 2008 22:06:59 GMT

!! Made this the Current release for all downlaods as i see more tarffic on this link than other release tabs
!! Here are the new additions to Ver 2.1. (Jun 20)
*Works with https:// or SSL based Installs. (SDK calls)*
- I Accept all Server Certificates. If you need to change the code look in the CrmConnection.myCertificateValidation implementation
*Shows the Endpoints returned by the Discovery service before making call to CrmService SDK*
- This allows you to change the endpoint from the client if Discovery service information is not correct for registering plugins. This usually is needed for IFD or for troubleshooting purposes
*Images for Parent and Subordinate entitities for Merge request*
- Now you can register an Image for Subordinate entity also for Merge request. You shall get a pop-up that asks if you need to register for Subordinate or parent

!! Sceanrios
* *Developer Scenario:* An ISV creates a plug-in and registers it on Contact Create as PreCallout (Aka BeforeMainOperation Plug-in). He can then debug the plug-in by registering on Disk. Once the errors are fixed, he can then update the pluginassembly to be uploaded to the database.
* *Deployment Scenario:* An ISV builds few plug-ins and registers on multiples steps. Images are registered on few of them. He tests them in the Dev environment but would like to port the registrations to a different organization. PluginRegistration tool supports Export and Import of the solution xml to solve this scenario.
* *Admin Console:* Couple of ISV installs their plug-ins on a Customer Organization. Admin at the Customer side saw some problems with “Contact Create” action. He would like to know what plug-in are fired and what the pipeline is for the “Contact – Create”. He then finds the trouble causing plug-in and disables it. So it is all about troubleshooting. PluginRegistration tool solves this problem by allowing Enable/Disable/Unregister operations on steps, plug-in.

!! Complete feature-set of the tool
# Register a pluginassembly, step and image. Validates the data before sending to CRM
# Update pluginassembly, step and image
# Unregister a pluginassembly shall cascade unregister all the children
# Enable, Disable a step
# Auto retrieve all CustomEntities information from the organization when registering the step
# Allows setting more values on step (e.g.: configuration, secureconfiguration, filteringattributes, etc.)
# Auto retrieve CustomAttributes on entity when registering images
# Search the pluginassembly, type, steps, images by names
# Visualize the status of the CRM Organization multiple views
## View by Assembly : What steps are registered on what plug-in
## View by Entity : What steps are registered on an entity(e.g.: contact)
## View by Message : What steps are registered on a message (e.g.: create)
# Shows the list of Microsoft Dynamics CRM 3.0 callouts registered in the organization
# Work with multiple organizations at the same time
# Exports the Xml in the same format that can be accepted by PluginDeveloper tool

UPDATED RELEASE: Plugin registration tool 2.1 (Jun 20, 2008)

Fri, 20 Jun 2008 22:05:10 GMT

Hi

As I have seen some key feature asks in the news groups, so I added some fucntionality to the tool and some stuff that helps you alleviate the pain. Please send the feedback.

Here are the new additions.
*Works with https:// or SSL based Installs. (SDK calls)*
- I Accept all Server Certificates. If you need to change the code look in the CrmConnection.myCertificateValidation implementation
*Shows the Endpoints returned by the Discovery service before making call to CrmService SDK*
- This allows you to change the endpoint from the client if Discovery service information is not correct for registering plugins. This usually is needed for IFD or for troubleshooting purposes
*Images for Parent and Subordinate entitities for Merge request*
- Now you can register an Image for Subordinate entity also for Merge request. You shall get a pop-up that asks if you need to register for Subordinate or parent

!! Sceanrios
* *Developer Scenario:* An ISV creates a plug-in and registers it on Contact Create as PreCallout (Aka BeforeMainOperation Plug-in). He can then debug the plug-in by registering on Disk. Once the errors are fixed, he can then update the pluginassembly to be uploaded to the database.
* *Deployment Scenario:* An ISV builds few plug-ins and registers on multiples steps. Images are registered on few of them. He tests them in the Dev environment but would like to port the registrations to a different organization. PluginRegistration tool supports Export and Import of the solution xml to solve this scenario.
* *Admin Console:* Couple of ISV installs their plug-ins on a Customer Organization. Admin at the Customer side saw some problems with “Contact Create” action. He would like to know what plug-in are fired and what the pipeline is for the “Contact – Create”. He then finds the trouble causing plug-in and disables it. So it is all about troubleshooting. PluginRegistration tool solves this problem by allowing Enable/Disable/Unregister operations on steps, plug-in.

!! Complete feature-set of the tool
# Register a pluginassembly, step and image. Validates the data before sending to CRM
# Update pluginassembly, step and image
# Unregister a pluginassembly shall cascade unregister all the children
# Enable, Disable a step
# Auto retrieve all CustomEntities information from the organization when registering the step
# Allows setting more values on step (e.g.: configuration, secureconfiguration, filteringattributes, etc.)
# Auto retrieve CustomAttributes on entity when registering images
# Search the pluginassembly, type, steps, images by names
# Visualize the status of the CRM Organization multiple views
## View by Assembly : What steps are registered on what plug-in
## View by Entity : What steps are registered on an entity(e.g.: contact)
## View by Message : What steps are registered on a message (e.g.: create)
# Shows the list of Microsoft Dynamics CRM 3.0 callouts registered in the organization
# Work with multiple organizations at the same time
# Exports the Xml in the same format that can be accepted by PluginDeveloper tool

UPDATED RELEASE: Plugin registration tool 2.1 (Jun 20, 2008)

Fri, 20 Jun 2008 22:04:49 GMT