Given that Infor failed to migrate the old Developer Forum to this new platform, despite me asking them to do so, I am raising this issue here, and it relates to Opera 3 SQL SE developers only.
The Pegasus Opers SQL SE DIT/EAT libraries (e.g. OperaIMS.dll, OperaCommands.dll, OperaClientDLL.dll etc.) have been developed to target .NET Framework 4.7.2.
This means that my SE development (DLLs), using the DIT, and the EAT, to access the Opera SE SQL Server databases, has been written using C#, targetting .NET Framework 4.7.2.
My customer, has been writing a website that will consume my DLLs but, as with any current .NET developer worth their salt, has developed using .NET targetting .NET Core 8. This is hardly surprising given that .NET Core has been available since 2016.
The issue, of course is that my .NET Framework DLLs are not compatible with my customer's .NET Core website.
An attempt to write a wrapper around my DLLs has also failed becuase Opera SE uses the Net.Tcp Port Sharing Service and, buried deep in the OperaIMS library, is a call to the set_PortSharingEnabled() method.
This method has been deprecated, by Microsoft, in later versions of .NET Core, and so attempts to call my DLL to connect to the Opera 3 server, crashed with error "Method not found: 'Void System.ServiceModel.NetTcpBinding.set_PortSharingEnabled(Boolean)'"
I'm currently at a grinding halt, with regards to this project, meaning man-months of wasted work, not to mention the commercial committments for the project.
Have any other Opera 3 SE developers encountered this issue and, more importantly, found a resolution?
I'm guessing not, otherwise I woud have hoped that pressure would have already been placed on Pegasus to provide a version of the DIT/EAT libraries that target .NET Core.
I have, of course, escalated this issue with Pegasus, via various avenues, and they are currently looking into it not that, with all due respect, there is likely to be a quick resolution.
Any thoughts would be much appreciated
Steve