Pros and Cons for using Only ONE plug-in per Entity/Message RRS feed

  • Question

  • Greetings.

    With large customization projects, we are often confronted with multiple plug-ins triggered by the same entity and the same message.

    I found it hard to prevent the possible interference of one or more of these plug-ins with one or more others and when a conflict is detected, it is time consuming to investigate and find out which plug-in(s) is(are) the culprit(s).

    That is why I was wandering what would be the pros and cons to have only one plug-in per entity/message.

    For example, instead of having 17 different plug-ins triggered on post creation of the account entity, we would have only one plug-in on post creation of account. The Execute method of this plug-in would then dispatch into 17 different branches of methods/classes in order to achieve the desired goals.

    Besides the obvious size and maybe concurrent development issues, what other pros and cons could there be?

    Thanks for your thoughts,

    Frank M.


    Friday, September 29, 2017 9:45 AM