Recently while trying to register the plugin, we got the below error Microsoft.Crm.CrmException: Plug-in assembly fullnames must be unique (ignoring the version build and revision number). —> Microsoft.Crm.CrmException: Plug-in assembly fullnames must be unique (ignoring the version build and revision number). It was because we were trying to register the assembly which was already…
Continue Reading Nishant Rana’s Article on their blog
Fixed – Plug-in assembly fullnames must be unique (ignoring the version build and revision number) – Dynamics 365 / Dataverse
Recently while trying to register the plugin, we got the below error Microsoft.Crm.CrmException: Plug-in assembly fullnames must be unique (ignoring the version build and revision number). —> Microsoft.Crm.CrmException: Plug-in assembly fullnames must be unique (ignoring the version build and revision number). It was because we were trying to register the assembly which was already registered…
Blog Syndicated with Nishant Rana’s Permission
More About This Author
Array
Dyn365CE27 November 2023Failed deleting solution. Solution dependencies exist, cannot uninstall / Remove unmanaged layer– Dynamics 365 / Dataverse
Dyn365CE21 November 2023Enable classic editor for build/release pipelines in Azure DevOps
Dyn365CE20 November 2023Write an email (Copilot) in Dynamics 365 Customer Service
Dyn365CE15 November 2023Ask a Question (Copilot) in Dynamics 365 Customer Service
