file location of interop.mfilesapi has changed

I believe that this is a by-product of a change in our build process.  I don't expect that it will change back, but I also would warn that relying on locations of internal DLLs is somewhat of a risky pattern; these are certainly not guaranteed to always be in the same location forever.

Can you advise on a realiable method that can be used to access the latest interop when the installer of our application is executed.  In the past we would get the version number from the registry keys, and then access the interop using a preset path.

Hi Leroux,

I am not aware that we have published such guidance, unfortunately.  I can think of some brute-force ways to find it but, even then, it's potentially brittle if there are multiple files in the installer with the same name.

would it be acceptable if we make a copy of the interop.mfilesapi.dll and place it directly into our application, instead of loading it from the installed version of M-Files.  We would then include new copies on occasion when we upgrade all the M-Files versions in our application.

As you know Leroux: my role changed some time ago.  I am here solely in some spare time between calls and other activities.  I cannot say that what you propose is okay or not.

If you want an official statement then you could reach out to support, or through your account manager, but I am unaware of our position on this (e.g. what is in any licence agreements etc.).

thanks, I will do so