Breaking changes in client libraries

lock
push_pin
done
Beantwortet
3

Hi,

When trying to upgrade SuperOffice NuGet packages from 11.1 to 11.10 we have found out the following breaking changes:

  • All client methods are now async. For example, in the IListAgent interface there is no GetTicketCategories method any longer, only GetTicketCategoriesAsync.
  • ToServicesXX methods disappeared.We used them to convert SoCore objects like SoCredentials to their version-specific WCF objects.

It's possible to fix the async stuff, but what to use instead of ToServicesXX methods?

 

22. Feb. 2026 | 07:50 AM

Alle Antworten (3)

Hi Dmitry,

SuperOffice.WebApi has always had async methods.

SuperOffice.NetServer.Services is the only package that ever has ToServiceXX methods, and there was never a 11.1 release, or 11.10.

I'm not sure how to process this forum post.

Best regards.

 

23. Feb. 2026 | 03:35 PM
Hi Tony,

Sorry for the confusion, I'm talking about upgrading the SuperOffice.NetServer.Services package from 10.5.5.982 to 11.6.1004.
Looks like there are no ToServiceXX methods in the 11.6.1004 version - there is no SuperOffice.CRM.Services.WcfProxy assembly in the package at all.
23. Feb. 2026 | 03:52 PM

Hi Dmitry Kuskov,

OK, that makes more sense. Yes, we made an announcement in 2024 about upcoming changes in NetServer. It's become async from the Services all the way to the lowest levels of the database access layer. There is a link in that thread to a YouTube video were we held a partner meeting to highlight the changes coming in v11, and what the thought were at the time on v12.

If there is no SuperOffice.CRM.Services.WcfProxy dll in the latest package that is not good. We'll look into that.

We sent out mailings dating all the way back to July 2023 were we recommended all using these SOAP proxies to migrated away from them and adopt SuperOffice.WebApi package instead. This contains HTTP RPC proxies that mirror the SOAP APIs (Agents and Carriers), minimizing impact on migration away from SOAP, which is WCF and considered legacy these days. SuperOffice.WebApi examples on GitHub - these work for both onsite and online. Only difference is the Authorization type used to populate the Authorization header.

Best regards!

23 h, 36 m vor | 08:19 AM

Hi Dmitry Kuskov,

Thank you for reporting this issue, and we have discovered why this happened. Here is a download link to obtain the SuperOffice.Services.WcfProxy.dll for 11.6.1004. We have corrected for the next onsite release.

22 h, 37 m vor | 09:19 AM

Antwort hinzufügen