COMING UP: Support for .NET Standard, Java 8 in the SDK and new SDK versioning scheme

We are planning to roll out some upgrades to the SDK in April based on customer feedback and also to meet the TLS1.2 standard.


Upgrade to .NET Standard

We are working on adding support for.NET Standard 2.0 in the Bing Ads SDK following many requests from our customers. With this change, the .NET flavor of the SDK will require .NET Framework v4.6 or above or .NET Core 2.0.

.NET Standard is a new framework designed to be platform-independent. If your application targets .NET Standard, it is guaranteed to run on any platform that supports some flavor of the .NET Framework.

We are targeting to release support for the framework in our April release. For more information on .NET Standard and how it relates to other .NET frameworks, refer to this article.


Upgrade to Java 8

As part of the April release, we’re also upgrading the Java SDK to require Java 8 at a minimum. This will allow the SDK to upgrade  to TLS1.2 protocol.

Note: In our previous announcement, we had erroneously indicated the SDK will require Java 7 at minimum, instead of Java 8.


Update to SDK versioning

Starting with the April release, we will be making changes to the SDK versioning scheme. The SDK version number will assume the format:

Vold .Vnew.SeqNumber


Vold is the older version of the API

Vnew is the newer version of the API

SeqNumber is the sequential number, restarts from 1 if Vold or Vnew changes.


For example, once the next version of the API, v12, is released, the SDK version will change to 11.12.1, where “11” represents API v11 which is the older API version, and “12” stands for the new version of the API and “1” is the first number in this sequence. Once API v11 sunsets, the SDK version number will change to 12.0.1, as ”12” will be the only version of the API until API v13.