tommalow / extendedplugin.cs

ExtendedPlugin.cs

Extended Plugin.cs which makes DAXIF# able to synchronize plugins to a CRM solution, without the use of the PluginRegistration tool.

Different version of the plugin.cs exist as DAXIF# PluginSync have been extended to incoporate more function in order to replace the use of

Example of how to use it can be found here.

For DAXIF# v2.2.0.7

Extended to handle user context for which a plugin can be executed under. Plugins can now accept a GUID of a user entity in the CRM system. The GUID will be tested if it points to a valid user entity in the system

For DAXIF# v2.1+

Extended to handle more parameters for steps

• Deployment Mode
• ExecutionMode
• Step Name
• ExecutionOrder
• FilteredAttributes

Images can also be added to a plugin with the parameters

• Image Name
• Entity Alias
• ImageType
• Attributes

For DAXIF# v2.1+

Extends plugin to enaable Daxif# to sync plugins with the parameters

• The full assembly name of the class containing the RegisteredEvents
• The Pipeline Stage
• The Event Operation
• Logical Entity Name (or empty for all)

extendedplugin.cs's Issues

EventOperation Enum

Hey, I'm looking into using this plugin base class and have a question about the EventOperation enum.

It looks like it only implements a subset of the available "EventOperations" or messages available to D365. E.g. it does not implement "Merge", "AddMember", "AddToQueue", and so on.

What is the reason for this? Is the intention for additional messages to be added to the enum as needed?

Also, I noticed the EventOperations enum numbering appears to be a sequence that would typically be used for a bit flag but I didn't see any implementation supporting that. Was there some other intent behind that?