821
Currently i have a D365 Plugin solution with over 20 plugins but I was wondering is it better to split these up in to smaller plugin solutions and have a several solution with maybe plugins for one entity type so you only ever work on the solution that relates to the areas you are working on. I will soon have an issue where there are multiple work streams coding on the same environment and think it would be better to split things up .
Thanks G
*This post is locked for comments
Hi gman,
I think that this might be a controversial question, and different people might give you different answers on this.
If you are the only person working on this implementation and the only person that will be doing updates to this, then maybe you can leave it as a single plugin solution. If there are multiple people in the development team, you can split it into multiple plugins and do not allow the same people to work on the same plugin.
Additionally, make sure that you are working within a Source Control environment, and even better have some sort of CI/CD integration. MVP Wael Hamze has developed some Continuous Delivery Integration tools that might make this easier for you, as well as the PowerApps CI/CD Tools. Check it out.
https://marketplace.visualstudio.com/items?itemName=WaelHamze.xrm-ci-framework-build-tasks
Hope this helps.
Hi,
As long as you have 1 (one) dll and multiple steps, i think there is no big benefits of having steps split into multiple solutions. If you want to safe and ease your deployments, i believe it'd better to split plugin dll into several dlls. You can take modules to do that, or entities if you have big amount of plugins per entity.
Regards,
#1
Mohamed Amine Mahmoudi
83
Super User 2025 Season 1
#2
Community Member
52
#3
Victor Onyebuchi
6
Share
Report
All responses (
Answers (
