The M-Files API COM Interop supports .Net 6/7?

Question

Hello, I am relatively new to the .net framework and I apologize if any vagueness is done. 
 After upgrading the .net version (from 4.8 to 6) in our machines, we lost the functions previously developed using the Mfiles COM API. Is this an expected behaviour, the COM API is not compatible with the .net 6? 
 If not, is there any alternative or a plan to make it compatible in the future? How about the rest API, would we face the same issue? Thank you again for the excellent support!

Craig Hawker · Accepted Answer

.NET is confusing. 
 .NET 4.x is referred to as ".NET Framework". It was designed to run on Windows machines only. The latest version is 4.8. Later versions within .NET Framework are backwards-compatible (e.g. .NET 4.8 applications can include .NET 4.5 binaries). 
 Microsoft have since released a number of .NET versions (Core, 5.0, 6.0, and now 7.0) that are capable of running on many operating systems. There are many things different between these versions and .NET Framework. Whilst there's a lot of similarity between these newer versions (e.g. between 6.0 and 7.0), none of these are backwards-compatible with any .NET Framework. 
 However. 
 The M-Files COM API is not a native .NET Framework assembly. It is a COM-exposed DLL which can be used from various environments including .NET. The fact you're using it from .NET Framework or .NET Core or .NET 6, or something outside of the .NET environment like Powershell, should be irrelevant; provided it can interact with COM then it should be fine. 
 I just tested it using a .NET 6.0 console application I happened to have available. I could connect to a vault and get a session, etc. 
 Therefore... 
 The issue shouldn't inherently be related to the .NET runtime you're using. What exactly is happening?

Craig Hawker · Answer

To answer your last question... 
 The REST API is fundamentally different, as you use HTTP requests to interact with it, rather than the COM interface. There are advantages (e.g. you can use any language or operating system to interact, as long as it can make HTTP requests) and disadvantages (e.g. the REST API does not have the breadth of functionality that the COM API does) to using the REST API. You pick your poison. 
 But: no, you shouldn't need to move just because you've updated the framework runtime you've targeted.

The M-Files API COM Interop supports .Net 6/7?

Top Replies