Microsoft Dynamics 365 | Integration, Dataverse...

One C# File per step or per message/entity for plugins?

(3) Share

Report

Posted on by akblyth

Hi guys. Currently our plugin assembly is structured in the following way. PostUpdateWorkorder.cs, PreUpdateWorkorder.cs, PreValidateUpdateWorkorder.cs, PostCreateWorkorder etc...all inside of the assembly. This follows on for all of our entities. We find ourselves having a lot of bugs within plugins, such as awkward loops and weird fixes to small issues. Should we have one file per entity that contains an execution method for all of the different messages (post, pre, prevalidate) or continute to do it the current way?

I have the same question (0)

All responses (2)

Answers (0)

Suggested answer

a33ik 84,331 Most Valuable Professional on at

Like (2)

Report
Copy link

Link copied!

Hello,

I would recommend having one plugin per scenario.

Was this reply helpful? Yes No
kalluu91 40 on at

Like (1)

Report
Copy link

Link copied!

If you don't have too many plugins, it's best to put all plugins in a single dll.

If you have multiple developers working on the same plugin, check this article for the plugin structure: https://kalcancode.wordpress.com/2025/02/14/power-apps-development-lifecycle-for-a-team-part-1/

Cheers,

Kim Anh

Was this reply helpful? Yes No