The LicenseSpring .NET SDK lets you implement license activation, entitlement enforcement, and usage tracking directly inside your C# or .NET application with no external licensing infrastructure to build or maintain.
Built for the full Microsoft ecosystem, the SDK supports .NET Framework, modern .NET runtimes, .NET Standard, and Xamarin, and covers desktop, enterprise, mobile, and cross-platform .NET products from a single integration.
ISO 27001 Certified
ISO 9001 Certified
Trusted by Software Vendors WorldwideThe .NET SDK integrates as a native library into your existing .NET codebase. Once installed, you have direct access to LicenseSpring's licensing infrastructure.
With the SDK, you can:
Activate and validate licenses at runtime: online, offline, or in air-gapped environments
Enforce node-locked, floating, subscription, and consumption-based licensing: using the model that fits your product
Gate features by entitlement: control access to functionality at the SDK level, across any .NET application type
Run local license checks with configurable grace periods: define how long the SDK honors a cached license before requiring revalidation, so connectivity loss never interrupts active users
Bind licenses to hardware: generate persistent hardware IDs using multiple device fingerprinting algorithms suited to the deployment environment
Track usage and activations: feed license telemetry back to the LicenseSpring platform in real time
The .NET SDK covers the full range of Microsoft and cross-platform .NET environments, enabling vendors to license applications built with C#, VB.NET, and other .NET-compatible languages.
| Use Case | Description |
|---|---|
Desktop Applications | Licensing for WinForms, WPF, and Windows desktop software |
Enterprise Software | Licensing internal tools and enterprise-grade .NET applications |
SaaS Companion Apps | Managing licensing for client-side applications connected to cloud services |
Mobile Applications | Licensing Xamarin.Forms Android and iOS apps |
Developer Tools | Licensing SDKs, developer platforms, and productivity tools |
The .NET SDK provides broad version coverage across legacy and modern .NET environments. Choose the runtime that matches your target deployment.
The .NET SDK is available as a NuGet package, integrating directly into your existing development workflow.
Package name: LicenseSpring.NetSDK
Supported target frameworks:
net5.0 · net6.0 · net7.0 · net8.0 · netstandard2.0 · netstandard2.1 · net45 through net48
The downloadable SDK ZIP package includes everything needed to start integrating licensing into your application.
Contents include:
Compiled libraries for .NET Framework, .NET Standard, and modern .NET runtimes.
Android
Console Applications
Forms iOS
VBA integrations
VB.NET
WinForms
Xamarin.Forms
Xamarin
Guides covering SDK initialization, license activation, runtime validation, feature entitlement enforcement, and offline activation flows.
Full changelog covering SDK updates, bug fixes, new features, and platform compatibility improvements.
The .NET SDK includes hardware fingerprinting support for node-locked licensing and device-bound activation. Multiple algorithms are available for computing a unique, persistent hardware identifier, selecting the approach that fits the deployment environment, whether that's a physical workstation, a virtual machine, or a Xamarin mobile device.
Generated hardware IDs are used for:
Node-locked license binding
Device identification and activation tracking
Consistent hardware fingerprinting across multi-SDK product deployments
Products that combine a .NET component with other parts of their stack, such as a C++ core engine, a Java backend, or a Node.js interface, can use multiple LicenseSpring SDKs simultaneously.
All LicenseSpring SDKs share a common license file format and compute hardware identifiers using the same underlying logic. A license issued to a device is recognized consistently across every component of your product, regardless of which SDK each part uses.
The .NET SDK fully supports deployments with limited or no internet connectivity, with two distinct activation paths:
Offline activation: uses a file-exchange flow for environments with occasional or restricted connectivity
Air-gapped activation: uses a code-exchange flow for environments where no external data transfer is permitted
Our developer support team can help you implement licensing quickly and correctly.
Full SDK documentation and API reference
Integration tutorials and code samples
Direct technical support