Needs to discuss about the best practices to write a plugin for Dynamics 365

(0) Share

Report

Posted on by Inkey Solutions

2,057

Hello Everyone,

Hope you are doing well.

This discussion is regarding to write a plugin code in one .cs file or multiple .cs file.

We have seen that many developers are using only one .cs file to manage the code of all the messages of the entity. At the other hand some of the developers are creating more than one .cs file based on the Message. Could anyone confirm what should be the best practice to manage the Plugins?

All responses (2)

Answers (0)

Ray 1,516 on at

Like (0)

Report

RE: Needs to discuss about the best practices to write a plugin for Dynamics 365

One file compare with multiple files:

Advantages:

1. Less plugin can cause less conflict in plugin registration.

Disadvantages:

1. Hight coupling.

2. Less flexable

3. Need consider deepth, order, trigger point, async/sync, etc.

So i vote for multiple files.

BTW, you can find the OOTB plugin in plugin registration tool and see how they do it.
a33ik 84,331 Most Valuable Professional on at

Like (1)

Report

RE: Needs to discuss about the best practices to write a plugin for Dynamics 365

Hello,

In my opinion - one plugin - one class, one cs file.

Where there could be a common base - I use base classes and put all the shared elements in it and inherit plugin classes from it.