Microsoft's released a new version of the.NET Framework that includes updates for ASP.NET, high-resolution displays and better profiling, among the enhancements. The.NET Fundamentals Team announced the.NET Framework 4.5.2 on its blog yesterday, calling it a 'highly compatible, in-place update to the.NET Framework 4, 4.5 and 4.5.1.' Jan 24, 2018 Microsoft.NET Framework 4.5.2 Multi-Targeting Pack Microsoft.NET Framework 4.5.2 Muliti-Targeting Pack (ENU) 3) Open Visual Studio 2013 and right click the project properties and found that.NET Framework 4.5.2 has listed under ' Target Framework ' dropdown for all the projects except SharePoint Projects.
A few days ago somebody raised a question in the community forums:
“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.”
Well, it’s hard to know what’s happening in various environments, so I made a note for myself but did not pay too much attention. That is until a few days later somebody else (yes, Rob K), mentioned that he could not import my TCS Tools solution into V9.
That sort of rang a bell, but I still did not make the connection right away.
Microsoft.NET Framework 4.5.2 Multi-Targeting Pack Microsoft.NET Framework 4.5.2 Muliti-Targeting Pack (ENU) 3) Open Visual Studio 2013 and right click the project properties and found that.NET Framework 4.5.2 has listed under ' Target Framework ' dropdown for all the projects except SharePoint Projects. Microsoft.NET Framework 4.5.2 or later is required on the CIC server. The Microsoft.NET Framework 4.5.2 or later is a highly compatible, in-place update to the.NET Framework 4.5.1, the.NET Framework 4.5, and the.NET Framework 4. However, it can run side by side with.NET Framework 3.5.1. For more information, see Microsoft KB article https.
Microsoft Net Framework 2.5 Download
To my surprise, I got exactly the same error when I tried importing TCS Tools into a new V9 trial a day or two later.
If you look at the thread there, you’ll find a response from Vladimir Karukes – basically, we need to specify 4.5.2 target for the plugin assembly to avoid the error. Turned out he was spot on.
In case with TCS Tools, here is what happened:
- I’ve always been building it using the on-prem version, and it works fine with 4.6
- So the target FW version of my assemblies used to be 4.6(?)
- At which point did it stop working in V9, I am not 100% sure, but, looking at that thread in the community forums, it seems there was some recent change
So yes, rebuilding for 4.5.2 did solve the problem.
Microsoft .net Framework 4.5.2 For Mac Download
Microsoft .net Framework 4.5.2 For Mac Iso
But, before I got to 4.5.2, I actually tried 4.7.2.. Guess what error message came up then? It was exactly the same error, but it was saying that my assembly was supposed to target 4.7.2 this time around.
In other words, the error message seems to be misleading – Dynamics seems to be looking at the actual target FW version of the assembly and just echoing that version number where it should be asking for 4.5.2(since it seems to be the highest supported version in the online environment).
PS. Still have to rebuild Configuration Data Manager tool, too, but that’s for tomorrow..
A few days ago somebody raised a question in the community forums:
“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.”
Well, it’s hard to know what’s happening in various environments, so I made a note for myself but did not pay too much attention. That is until a few days later somebody else (yes, Rob K), mentioned that he could not import my TCS Tools solution into V9.
That sort of rang a bell, but I still did not make the connection right away.
To my surprise, I got exactly the same error when I tried importing TCS Tools into a new V9 trial a day or two later.
If you look at the thread there, you’ll find a response from Vladimir Karukes – basically, we need to specify 4.5.2 target for the plugin assembly to avoid the error. Turned out he was spot on.
In case with TCS Tools, here is what happened:
- I’ve always been building it using the on-prem version, and it works fine with 4.6
- So the target FW version of my assemblies used to be 4.6(?)
- At which point did it stop working in V9, I am not 100% sure, but, looking at that thread in the community forums, it seems there was some recent change
So yes, rebuilding for 4.5.2 did solve the problem.
But, before I got to 4.5.2, I actually tried 4.7.2.. Guess what error message came up then? It was exactly the same error, but it was saying that my assembly was supposed to target 4.7.2 this time around.
In other words, the error message seems to be misleading – Dynamics seems to be looking at the actual target FW version of the assembly and just echoing that version number where it should be asking for 4.5.2(since it seems to be the highest supported version in the online environment).
PS. Still have to rebuild Configuration Data Manager tool, too, but that’s for tomorrow..