sdk 2025 - error

0

Hi Franek,
SDK add-ons usually work only within a specific version range (e.g. 2020.x.x.x). When upgrading to a newer version, the SDK needs to be adjusted accordingly. This can be done independently if you have a license, or outsourced to a third-party company or the original vendor.

Hi Franek

Don't know how you've built the package. I'm using the standard "WEBCON BPS SDK Tools" to build the packages.
With 2025 the structure of the json file changed and now also includes version and dependencies. I specially love the dependencies, as these were a bit of a challenge in previous versions of the SDK.

{
"extensions": [
{
"guid": "b28855a7-c35b-45b4-a80d-62c4249a2996",
"name": "Abacus - Create Debitor",
"description": "Creates a new debitor",
"assembly": "Demo",
"class": "Demo.CustomActions.CreateDebitor",
"type": "CustomAction"
}
],
"dependencies": [
"Demo"
],
"version": "25"
}

Edited:
Missed a part in your sentence.
Shalassin is right, 2025 is more restrictive in checking either the SDK licence or the signature of the assembly. Signature must be from a trusted provider, usually a WEBCON partner or WEBCON itself.

We implemented some Extensions to call Abacus SOAP Services on 2025. Guess it is quite similar of what you are doing. Works perfect.

I've updated the SDK to the 2025 version. I'm also using the WEBCON BPS SDK Tools. I have several SDKs, but only the ones that use an external library (also written by me) are not working. I use svcutil to create wcf class.

Pretty much the same way I did.
Is the external library also based on .net standard?
Guess you already added the library to the dependencies to other assemblies in your json file.
I have packages, where I had to add three and more additional dependencies because they were nested.

Hi,

Starting from the 2023 release, we migrated our solution from .NET Framework 4.7.2 to .NET 6. During this process, we encountered some limitations introduced by Microsoft — in particular, restricted support for certain WCF bindings.

The issue you're experiencing seems similar to what we faced at that time. You might find this StackOverflow thread helpful:
https://stackoverflow.com/questions/52182419/unable-to-consume-wcf-wshttpbinding-in-net-core

Hopefully, it will point you in the right direction!

Best regards,
Łukasz

I was already aware of that issue. The solution was to update the dependencies(to the latest compatible version for .NET Standard 2.0) in my external library (SOAP client).