Client Components

To leverage the powerful licensing capabilities of Babel Licensing in your .NET applications and software components, you need to install the Babel Licensing client components. These components, including the Babel Licensing NuGet package and the Babel Data NuGet package, provide the necessary tools and functionalities to seamlessly integrate licensing features into your projects. This introduction will guide you through the process of installing these client components and give you an overview of their role in enabling effective license management.

Babel NuGet Packages

With the purchase of a Company license, you received several NuGet packages containing the Babel Obfuscator and Babel Licensing CLI tools for dotnet:

PackageDescription

Babel.Licensing.Tool.x.y.z.nupkg

Babel Licensing dotnet CLI tool

Babel.Licensing.x.y.z.nupkg

Babel Licensing client library

Babel.Data.x.y.z.nupkg

Babel Licensing Database compomponents

These NuGet packages are not available on the public NuGet repository. To use them in your projects, you need to install them on your private NuGet feeds or your local machine.

There are several NuGet private feeds available:

If you don't have a private NuGet feed, you can create one on your local machine.

Regardless your packages are hosted on a server or your local machine, you can access them using the nuget CLI tool or Visual Studio.

Create a Local NuGet Feed Using dotnet

If you have installed Visual Studio or dotnet SDK, you can access NuGet directly from the dotnet CLI tool. Now you have to decide where to store your packages on your local machine. For this example, we will create the folder NuGet under the user Documents folder. If you are on Linux or Mac OS, you can create the folder under the user home directory ~/NuGet.

You can add the packages to your local feed using dotnet nuget add command.

Windows PowerShell or DOS shell:

dotnet nuget add Babel.Licensing.Tool.10.0.0.nupkg -Source %UserProfile%\Documents\NuGet

Linux or Mac OS:

dotnet nuget add Babel.Licensing.Tool.10.0.0.nupkg -Source ~/NuGet

The dotnet tool should report that the package was successfully added, and you can now access your packages through the dotnet command.

Create a Local NuGet Feed Using Visual Studio

To install the NuGet package in your local machine, open Visual Studio and from the Tools menu select Options. In the Options panel, search for NuGet and select the Package Sources node under the NuGet Package Manager tree item.

Press the button with the plus icon and enter the Name field Babel and the Source field the full path to the folder containing the Babel NuGet package files. Press the OK button.

To reference Babel.Licensing NuGet package. In the Solution Explorer, right-click your project file. Select Manage NuGet Packages…

Select your newly added Babel package source in the Package source combo box, then Install the Babel.Licensing package.

Copy your license file babel.licenses in the solution folder and rebuild the solution.

Installing Babel Licensing Lic CLI Tool

Once the Babel NuGet packages are in your local NuGet repository, you can install the CLI tools using dotnet tool install command.

Install Babel Obfuscator CLI tool babel:

dotnet tool install Babel.Licensing.Tool -g

Install Babel Licensing CLI tool lic:

dotnet tool install Babel.Licensing.Tool -g

To show the versions of the dotnet tool installed, use the following command:

dotnet tool list -g

Package Id                 Version      Commands
------------------------------------------------
babel.licensing.tool       10.0.0       lic     
babel.obfuscator.tool      10.0.0       babel   

Last updated