Avalara.AvaTax.SoapClient 16.8.2

Avalara AvaTax SOAP Client

Avalara.AvaTax.Adapter — the SOAP (ASMX) client for the AvaTax service.

Platform: .NET Framework 2.0 or later, Windows only. This library uses ASMX SOAP (System.Web.Services), MSMQ (System.Messaging) and COM interop, none of which exist on .NET Core / .NET 5+.

What's new in 16.8.1

Adds Profile.ClientSupportMultiTax, which tells the service that your client understands multi-tax responses. It is sent as the ClientSupportMultiTax element of the Profile SOAP header and defaults to false, so nothing changes until you opt in.

using Avalara.AvaTax.Adapter.TaxService;

TaxSvc svc = new TaxSvc();
svc.Profile.Client = "MyIntegration,1.0";
svc.Profile.ClientSupportMultiTax = true;   // opt in

The resulting SOAP header:

<Profile xmlns="http://avatax.avalara.com/services">
  <Name>...</Name>
  <Client>MyIntegration,1.0</Client>
  <Adapter>...</Adapter>
  <Machine>...</Machine>
  <ClientSupportMultiTax>true</ClientSupportMultiTax>
</Profile>

Because the element is optional in the service contract (minOccurs="0"), older services and stored payloads that omit it still deserialize correctly, defaulting to false.

Upgrading from 16.8.0

This is a drop-in upgrade. AssemblyVersion remains 16.8.0.0, so existing direct references and binding redirects keep working without changes — only AssemblyFileVersion moves to 16.8.1.0. The release adds the property above and removes no public API. In particular:

• TaxType and every other enum keep their exact numeric values, so values you have persisted to a database or serialized to disk continue to mean the same thing.
• Password-related API (RequestSecurity.Password, UsernameToken.Password, CompanyReturn.EfilePassword) is unchanged.

One small caveat carried over from source changes made after 16.8.0 shipped:

• Members of Avalara.AvaTax.Adapter.LogService.LogLevel were re-cased from DEBUG, INFO, WARNING, ERROR, FATAL, NONE to Debug, Info, Warning, Error, Fatal, None. The numeric values are unchanged, so only source that names them needs updating. Note the separate Avalara.AvaTax.Adapter.LogLevel enum still uses the original upper-case names.
• The LogSvc.LogMessage(string, LogLevel, string) overload was removed.

Configuration

This package does not ship an Avalara.AvaTax.Adapter.dll.config. Add the following to your application's config file and supply your own values:

<configSections>
  <sectionGroup name="AvaTax">
    <section name="ServiceConfig"   type="Avalara.AvaTax.Adapter.XmlSerializerSectionHandler, Avalara.AvaTax.Adapter" />
    <section name="RequestSecurity" type="Avalara.AvaTax.Adapter.XmlSerializerSectionHandler, Avalara.AvaTax.Adapter" />
  </sectionGroup>
</configSections>

<AvaTax>
  <ServiceConfig>
    <Url>https://avatax.avalara.net/</Url>
    <RequestTimeout>300</RequestTimeout>
  </ServiceConfig>
  <RequestSecurity>
    <Account>YOUR_ACCOUNT_NUMBER</Account>
    <License>YOUR_LICENSE_KEY</License>
  </RequestSecurity>
</AvaTax>

Never commit real account or license values to source control.

License

Apache License 2.0. Full text: https://www.apache.org/licenses/LICENSE-2.0

Third-party components

This assembly statically includes Apache log4net (https://logging.apache.org/log4net/), Copyright The Apache Software Foundation, also licensed under the Apache License 2.0. Its types appear in this assembly as an implementation detail and are not supported API.

Support

http://developer.avalara.com/