hi Mosman Council 

Try the following for information,
OpenText Content Manager SDK 23.3 and 23.4: Welcome to the Content Manager SDK Documentation (content-manager-sdk.github.io)
This has links to 

• The SDK Forum
• David Churchland's Integration Blog 

Thank Martin. Unfortunately, microFocus.ContentManager.SDK (23.4.0.58) cannot be fully compatible with .NETFramework Version = v.4.8.1. (.net core Web API). Do you have another alternative solution?  

Is there a reason why you are on .NET Core?

Upping to .NET Standard should then allow you to use the .NET Framework SDK.

Alternatively, if your solution is locked into .NET Core, you can use a generic REST client or your favourite flavour of .NET Core compatablie REST package to craft and make REST API calls to an installed Content Manager ServiceAPI endpoint.

-Scotty

If you're referring to the warnings visual studio gives you when adding the packages, you can safely ignore them - you won't be able to target linux platforms but otherwise the packages work fine in dotnet (core)

Thank Scotty. We have developed a lot of APIs based on .net Core 8. That is why we prefer to use .net Core. 

In that case you are all good.

Apologies as I blame Microsoft for all the different .NET Versions which doesn't make it easy.

.NET Framework  The original version of the .NET Platform
.NET Core  A cross platform version of .NET that was originally developed to overcome some limitations of Framework
.NET Standard  An intermediary version that made it possible to run on .NET Framework, and .NET Core
.NET (Version 5 and above)  Convergence of both .NET Core and .NET Framework into a single platform moving forward (Technically has 'core' in the name still but most people don't include it to help simplify the numbering and to help tell the different editions apart)

.NET 8 (.NET Core 8) shouldn't have any noticeable issues trying to make calls to the CM .NET Framework SDK.

For myself, I tend to associate '.NET Core' with versions prior to .NET 5 before the convergence took place.

As Jan mentioned - should be good to ignore any warnings but for any app, make sure you have unit tests to cover your scenarios just in case 

-Scotty

I've been using the TRIM SDK with Dot Net core/non framework/converged/whatever you want to call it for quite a while (versions 5,6 and 8).  It works as expected but there are a couple of things you need to be aware of.  The TRIM SDK requires the DLLs "System.Diagnostics.EventLog" and "System.Security.Permissions" to write messages to the Windows event log.  These DLLs are not part of the standard dot net core runtime bundle and you'll need to make them available to your application.  Adding the nuget packages for these DLLs works for me.

If these DLLs aren't available to your application then your application will throw exceptions with messages that aren't totally helpful.