You’re offline. This is a read only version of the page.
Hi,
We recently moved from CRM 2013 On-premise to Dynamics 365 Online Version 9 and I have a question related to assemblies (Plugins and custom workflow assemblies).
I read on the Microsoft Dynamics site, Only the .NET assemblies that are created with the Microsoft .NET Framework 4.5.2 or later for use in Dynamics 365 as a Dynamics 365 plug-in assembly or as a Dynamics 365 custom workflow activity is supported. ( https://docs.microsoft.com/en-us/dynamics365/customer-engagement/developer/supported-extensions )
We have few plugins and workflow assemblies which were built on .NET Version 4.0.0.0 and referencing Microsoft.Xrm.Sdk assemblies with Version 6.0.0.0. So is there any easy way that we can upgrade all our dll's to point to .Net Version 4.6.2 and latest XRM asemblies? Please suggest?
Or do we need to recompile all our source code and add the latest XRM SDK references to the source code (Which is a lot of work involved I believe).
Could someone please suggest the best possibilities to upgrade the DLL's.
Many thanks in advance.
Thank you for looking into my query and for answering.
You will need to load the source code and recompile the DLL's. Sadly it's unavoidable as your existing compiled versions are hard coded to a version of .Net and the assemblies they were built for.
At the same time, as you are moving from on-premise to online I had better remind you that there there is a difference in what actions can be performed within a plugin online as all plugins can only run in sandbox mode (and I suspect your existing plugins may be performing tasks that may not be allowed in Sandbox mode. jerhome.blogspot.com/.../ms-crm-2011-plugin-sandbox-mode.html gives a good overview of what the differences are and things that sandbox mode plugins can no longer do.
Finally there are a lot of changes between CRM 2013 and Dynamics 365 version 9. Now would be a good time to look at your entire solution and identify any bits of custom development which can now be performed by out of the box standard functionality (things like roll-ups and calculated fields) and start to re-implement those functions with the out of the box solution.
Share
Report
All responses (
Answers (
6,350