Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1 Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
Hi, yesterday in one of our customers with v9 online, any attempt to update a plugin produces the following message:
Currently, Microsoft Dynamics 365 requires the .NET Framework version 4.6.2 for plug-in assemblies. Rebuild the assembly with the .NET Framework version 4.6.2 and try again.
I am pretty sure we are building the plug-ins using version 4.6.2 (with VS 2015), and we are using SDK libraries obtained from NuGet, but D365 still shows the same error. As usual, I would appreciate your guidance and advise.
It is worth noting I am getting this error now for plugins that have not been changed recently and previously had no issues, but now if a solution includes these thy are failing on import to live.
We are also getting this error for Workflow assembly, this is really anyoing :-(
Try to switch to 4.5.2. If you are using ILMerge, make sure it won't put CRM SDK DLLs back into the build folder.
The error message is misleading, apparently. Ran into this issue with my plugins tonight as well - looks like V9 used to accept 4.6 target, but something has changed and it's not, anymore.. so Vladimir is correct - switching to 4.5.2 does help. But the error message is misleading since it's actually asking for 4.6.2 when the assembly is compiled for 4.6.2. And it's asking for 4.7.2 when the assembly is compiled for 4.7.2.. none of that is correct.
I have the same issue.
4.5.2 doesn't work and 4.6.1 or 4.6.2 I can't register\update.
Week ago I've successfully updated 4.6.2. But for now I can't do the same as before.
Have a look at your assembly in JustDecompile (from Telerik) or some other tool - make sure it's actually targetting 4.5.2 when you are looking at it that way
The issue is misleading and inconsistent. In My organisation the below things Happened
1. If Plugin assembly and workflow assembly both are in 4.6.2, it fails
2. If Plug in is in 4.52 and workflow is 4.6.2 things works fine
For a temporary fix change the version to 4.5.2 it should work as it worked for me
Changing .NET framework to 4.5.2 worked for me as well
We were using .NET Framework 4.7.1 for the target framework for plug-ins last week. We are using Dynamics 365 V 9.0 online. The plug-in registered fine. This morning it stopped working. We were getting this error:
"...This plugin assembly uses version xxxxxxxxxxxxx, Version=126.96.36.199, Culture=neutral, PublicKeyToken=xxxxxxxxxxxx of the .NET Framework. At this time Microsoft Dynamics 365 requires version 4.7.1 of the .NET Framework for plugin assemblies. Rebuild this assembly using .NET Framework version 4.7.1 and try again...."
We switched to 4.5.2 and it works. Tried 4.6.1 and 4.7.1 again and get the same error.
I keep getting the same error. None of the builds is working for me. Any suggestions?
pskamble1, You would need to provide a bit more information in order for anyone to help you. A common solution has been to switch to .NET 4.5.2.
I did try to change the build to 4.5.2 even tried 4.6.2 and 4.7.1 But I still get this error-
This plugin assembly uses version XXX, Version=188.8.131.52, Culture=neutral, PublicKeyToken=XXX of the .NET Framework. At this time Microsoft Dynamics 365 requires version XXXX of the .NET Framework for plugin assemblies. Rebuild this assembly using .NET Framework version XXXX and try again.
This plugin was working fine before. I am just trying to update some content in the plugin.
There are a couple of things causing confusion here.
1. The last few versions of Dynamics 365 require .NET version 4.5.2 for plugins as outlined at docs.microsoft.com/.../write-plugin
2. Dynamics 365 v9 recently started strictly enforcing this requirement when it didn't before.
3. There is a product defect in the error message thrown, where the current .NET version of the assembly is shown instead of "4.5.2".
If you're absolutely sure that you're building against 4.5.2 and still seeing this error, there is something else going on. But, the majority of these posts should fall in to the above category.
Bottom line: You must use .NET 4.5.2.
Business Applications communities