A few days ago somebody raised a question in the community forums:
- Microsoft .net Framework 4.5.2 For Mac 64-bit
- Microsoft 4.5.2 Framework Download
- Microsoft Net Framework 4 5 Download
“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.”
The Microsoft.NET Framework 4.5.2 is a highly compatible, in-place update to the Microsoft.NET Framework 4 and the Microsoft.NET Framework 4.5. The web installer is a small package that automatically determines and downloads only the components applicable for a particular platform. The Microsoft.NET Framework 4.5.2 is a highly compatible, in-place update to the.NET Framework 4 and 4.5.1. By using the.NET Framework 4.5.2 together with the C# or Visual Basic programming languages, you can write Windows Metro style apps. The.NET Framework 4.5.2 delivers better performance, reliability, and security. The Microsoft.NET Framework 4.5.2 is a software component which can be added to the Microsoft Windows operating system. It provides a large body of pre-coded solutions to common program requirements, and manages the execution of programs written specifically for. 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.' Microsoft.NET Framework 4.5.2 (Offline Installer) for Windows Vista SP2, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2008 SP2, Windows Server 2008.
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
Microsoft .net Framework 4.5.2 For Mac 64-bit
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..
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.
Microsoft 4.5.2 Framework Download
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).
Microsoft Net Framework 4 5 Download
PS. Still have to rebuild Configuration Data Manager tool, too, but that’s for tomorrow..