Migrate MIM Service activities to the latest version of the .NET framework.
With the MIM Service stuck at .NET Framework 3.5, this adds an extra pre-requisite to deploying the service on modern OS, and forces development on a old platform. It also reflects poorly with potential purchasers that the product if so far out of date with the Framework versions.
We are looking at the upgrading to .net version. At the moment we know we can’t go to .net 4.5 due to the dependant component change.
More to come as we perform a deep dive
-David, MIM Engineering Manager
Greene, Jeff (Radnor) commented
Any updates? Any hope?
Jordan Mills commented
Been a couple of years now. This is starting to become a blocking issue.
Marc Mac Donell commented
+1 to prioritize. We're running into roadblocks trying to develop workflows for new clients on Windows Server 2016 and Visual Studio 2017. Microsoft .NET Framework 3.5 has been deprecated since 2012.
Heinrich Peters commented
Please prioritize this one, VS2017 does not support .NET 3.5 WFs anymore... See: https://developercommunity.visualstudio.com/content/problem/26418/legacy-workflow-foundation-project-wont-load.html