.NET Framework 4.6 causes incompatibility with M-Files for certain operations
Posted by Lassi Lehtinen (M-Files) on 01 June 2015 03:04 PM
.NET Framework 4.6 causes some compatibility issues with M-Files.
In practice, this means that federated authentication (SAML V2.0, AD FS, OAuth, Azure AD sync) and replication via cloud storage do not work in the M-Files versions mentioned,
if the computer has .NET Framework 4.6 installed prior to installing M-Files.
This happens because certain modules of M-Files require .NET Framework 4.5 to be installed in order to be registered.
Version 4.6 is an "in-place upgrade" over 4.5, and after the upgrade M-Files assumes that 4.5 is not installed. As a result, M-Files does not register the modules that depend on .NET Framework 4.5.
The error message from M-Files is "Class not registered".
Note, however, that the "Class not registered" error message is a generic error message and may appear in several other unrelated circumstances, too.
For any additional questions regarding this topic, please contact M-Files Customer support: http://support.m-files.com
2015 M-Files Customer support team, http://support.m-files.com