We have written a library that wraps functionality around an IBM FileNet.Api.dll. We have been transitioning our library to use the .net core 5 app and attempting to connect to FileNet, we run into the below problem while fetching object-store instance.

Could not load type 'System.ServiceModel.Channels.MtomMessageEncodingBindingElement' from assembly 'System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.

Do we have FileNet.Api.dll supported in .net core 5 or is there any solution for the above issue?

As documented in the SPCR reports for FileNet Content Manager (under Supported Software > Runtime environment) we don't currently support .Net 5.0.

And as documented in the same report under Operating System > Windows, we don't support Windows Server Core as it does not include all the "bits" needed for a FileNet Content Manager environment.

You can view the report here: https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=494C1000CBA711EA92B4FC8223E18670&osPlatforms=AIX|Linux|Windows&duComponentIds=S007|S006|S003|S004|S008|S010|S005|S009|C012|C013|C011|C001&mandatoryCapIds=30|9|132|20|26&optionalCapIds=380|12|128|35|19|16|27

hey there,

is their an update that a new filenetAPI support .net?

regards

I am not sure if you speak about P8 FileNet .NET API or for FileNET Panagon / API .NET but in both cases there is no update. as I remember the P8 .NET API has a last version in 2017 and also the FileNet Client Panagon API a long time ago.  

but you may also check here Overview - Product lifecycle - IBM Support

You do have some alternatives such as using CMIS API (not my preference) or wrap the FN DLL into a 4.8.1 .net framework rest web api app.  I recently did this for CRUD actions on documents, searches and some other commonly used ECM methods.  That was straightforward let me know if you need some help or sample project to get started.