Versioning policy

We release a new version with new features, enhancements, and bug fixes at least once a month. In this guide we describe our versioning policy and principles we use when choosing the version for a new build.

Version format

DotNetBrowser version format is MAJOR.MINOR.PATCH, where:

• The MAJOR version is incremented when the significant backward-incompatible API changes are made. For example, this can happen when new language features are used or the architecture of the library has been significantly changed;

• The MINOR version is incremented when the API has been extended with new functionality. The changes in the API might be backward-incompatible, but most of the time they are backward-compatible;

• The PATCH version is incremented when some enhancements or fixes are made. The API is untouched in this case.

Early-access program (EAP) builds

Once we fix a bug or implement a new feature, we prepare and publish a new EAP build you can try before the fix or feature goes into production.

You can obtain an EAP build using one of the following ways:

Direct download

.NET Framework https://storage.googleapis.com/cloud.teamdev.com/downloads/dotnetbrowser2/eap/dotnetbrowser-net45-VERSION-eap.zip
.NET Core (includes WPF and WinForms)
https://storage.googleapis.com/cloud.teamdev.com/downloads/dotnetbrowser2/eap/dotnetbrowser-netcore30-VERSION-eap.zip .NET Standard (cross-platform)
https://storage.googleapis.com/cloud.teamdev.com/downloads/dotnetbrowser2/eap/dotnetbrowser-netstandard20-VERSION-eap.zip

You need to replace VERSION with the required EAP build number (e.g. 2.10.1-b2191).

To get notifications about the latest EAP builds follow @DotNetBrowser on Twitter.

NuGet feed

https://pkgs.dev.azure.com/teamdev-products/66fbd081-377c-4af2-a64d-fee8ca740ed4/_packaging/dotnetbrowser-eaps/nuget/v3/index.json

To add the above package source, take the following steps:

1. In Solution Explorer, right-click either References or a project and select Manage NuGet Packages…
2. Select the Settings icon in the Package Manager UI in the top right corner.
3. Click on the “+” button to add new source.
4. Edit the name, enter the URL in the Source control, and select Update.
5. Select OK to close settings window.

Make sure to check the “Include prerelease” option to get the list of available EAPs.

Alternatively, it is possible to add new package source to NuGet.Config file via Package Manager Console in Visual Studio using the below command:

dotnet nuget add source "https://pkgs.dev.azure.com/teamdev-products/66fbd081-377c-4af2-a64d-fee8ca740ed4/_packaging/dotnetbrowser-eaps/nuget/v3/index.json" --name "DotNetBrowser EAP NuGet feed"

There are multiple NuGet.Config files in different locations that store project-, user-, and computer-wide settings. More information is provided in the MSDN article.