NetServer web service proxies
WebApi client proxy
The WebApi Client offers an alternative to the existing SuperOffice NetServer WCF proxies. SuperOffice.WebApi has the exact same Agent-style services as SuperOffice.NetServer.Services while adopting modern practices, such as asynchronous methods.
This library is a .NET Standard 2.0 library that works with both .NET Framework (4.6.1 and higher) and .NET Core (2.0 and higher) applications.
This library makes it easier to work in a multi-tenant environment. It isolates a tenant's context in a WebApiOptions instance, where each instance is configured to target one specific tenant. Each instance can be configured with its own language, culture, and timezone settings.
This library also has built-in system user token support.
SOAP client proxy
If your services are configured to use SOAP, each method call is a SOAP envelope that will travel over the network. SOAP calls can be made by your preferred client, such as .NET.
There is flexibility in using SuperOffice proxies.
- Use NetServer proxies (NuGet packages)
- Generate a custom proxy by adding a web service
The most complete way is to reference the NuGet packages. You can either:
When necessary, use a tool to generate a client proxy class for a particular NetServer web service, for example, Appointment.svc or Contact.svc.