Note: Advice in this article will only work for DotNetBrowser 1.
See the corresponding article for DotNetBrowser 2 here.

When you purchase a commercial licence, you get an archive with two licence files inside:


You need to include one of these licence files in your MS VS2013 Project to enable the licence. The difference between the Development and Runtime licences is the following:

  • You can use the Development licence for development purposes only. The number of licences should be equal to the number of developers who use DotNetBrowser in development. For example, if you have 10 developers involved in your project and only 4 of them work with DotNetBrowser, you should purchase 4 licences only. 
  • The Runtime licence should be used when you distribute your software with DotNetBrowser enclosed. You can distribute your application with an enclosed Runtime licence to an unlimited number of end users.

There is often a need to replace the development licence with the runtime licence when preparing a release build of your software. Such cases are usually resolved by creating a dedicated build configuration in Visual Studio and configuring the pre-build event that will replace the licence file itself right before build.


The Per-Developer licence is recommended for 1 developer and can be used in the unlimited number of projects.

Buy Per-Developer Licence


The Project licence is recommended in case of a single project and unlimited number of developers working on it.

Request Project Licence


The Company-wide licence is recommended for unlimited number of projects and developers.

Request Company-wide Licence