Dynamics 365 Plugin Assemblies. Single or Multiple? You decide!

Organizing and managing plugin assemblies for your Dynamics 365 projects can pose a challenge. While there may be an obvious need for multiple plugins to fulfill your requirements, determining the optimal balance between maximizing deployment segregation and ease of deployment/visual studio can prove tricky.

Most projects require more than one plugin class per assembly. However, deploying multiple plugin classes within a single assembly can lead to issues with versioning and asserting that the correct plugin is being updated. Thus, this tutorial suggests that balancing these concerns may necessitate having a single plugin class per plugin assembly.

Ultimately, the decision on whether to use single or multiple plugin assemblies depends on your project's specific requirements. By weighing the pros and cons outlined in this tutorial, you can make a more informed decision that best serves the unique needs of your project.

So if you're grappling with this plugin assembly issue, check out the insights presented in this tutorial for guidance.

This post was originally published on the Inkey Solutions blog.