Many of us use the Microsoft Dynamics 365 Developer Toolkit for plugin development. This tool helps developers avoid manual tasks and helps them focus on implementing the business logic. Unfortunately, this tool is no longer working since the switch from Regional Discovery service to the Global Discovery service. Actually, the error “FCB ‘EnableRegionalDisco’ is disabled” is generated when connecting to the Dataverse environment.
On this blog, I will propose a workaround to solve this problem and continue to use the tool for the development and maintenance of your plugins by connecting to a Dataverse environment using the Global Discovery Service.
Before starting, this is the configuration used on my personal environment. Indeed, I use the following versions:
- Plug-in Registration Tool version 126.96.36.199
- Crm Sdk Bin (CoreTools) version 188.8.131.52
You can download the same versions of the SDK tools using the following PowerShell script:
Also, we will need the latest version of the SDK. The PowerShell script to use is shared on the docs: https://docs.microsoft.com/en-us/powerapps/developer/data-platform/download-tools-nuget#download-tools-using-powershell
To make it easier to follow the steps, below are the two directories used:
Now it is time to go to the folder that corresponds to the Visual Studio extension of the Microsoft Dynamics 365 Developer Toolkit. In my case, this is the path used:
Then, we need to replace the following Dll files of the extension by those of the last version of the registration tool plugin:
After re-starting Visual Studio, the tool should connect smoothly to a Dataverse environment using the Global Discovery Service:
Be prepared, we are halfway there. Indeed, after being able to connect to the CRM using the Global Discovery Service. An error is generated when deploying a plugin: “Could not load file or assembly ”CrmLibraries, Version=184.108.40.206, Culture=neutral, PublicKeyToken=31bf3856ad364e35 or one of its dependencies. The located assembly’s manifest definition does not match the assembly reference.“
To resolve this issue, we need to replace the following Dll files of the Plugin registration tool used in the tool path by those of a version 8 of the registration tool:
You can download the version 8 on this link: https://www.microsoft.com/en-us/download/details.aspx?id=50032
Finally, after all this manipulation. I can manage to connect to a Dataverse environment and deploy my plugins with the tool while using the global discovery service. Finally, the process shared on this blog may not work for you. It depends strongly on the version of the SDK used. I highly recommend using the same version I used.
Hope it helps…
Edit: For the moment, only the connection and the deployment are functional. Indeed, the Entity class generation and the creation of a new plugin is not functional for the moment. I will edit this Blog as I can find fixes. The next step will be to fix the error generated when creating a new plugin.