If I set up the watchdog timer each time I run a command in my program is it using the same instance internally, recreating, or adding a completely new timer with duplicate callbacks?

 Setting up the watchdog stops the current instance (stops the timers), creates a new watchdog instance and starts it again.

If I use the watchdog timer for floating and non-floating licenses, is there any need for me to call license.Check (online), since it seems like internally the timer is checking online and will throw all exceptions?

Watchdog, while running, will periodically call the Check method on the license object it was run on, regardless if the license is floating or not.

Do 'license.Register' and license.Check  have same functionality?

Yes, they are doing exactly the same thing

This document provides insights into the behavior of the watchdog timer and license functions. Learn how setting up the watchdog activates a new instance and understand its periodic Check method for license verification. Discover the similarities in funct

.NET/C#

License API changelog

LicenseSpring Documentation

Explore the documentation and learn how to use LicenseSpring.

Introduction

Basic Concepts

Opening an Account

Creating & Configuring Products

Integrating SDK and Configuring License Fulfillment

Activate a Key-Based License

Issuing New Licenses

License Detail View

Order Detail View

Customer Detail View

Metadata

Analytics

Users

Email Notifications

Roles/Permissions/User Labels

Audit Log

Billing

Settings

Vendor Platform

Product Features

Product Custom Fields

Product Versioning

Air-Gapped License Policy

License Policies

Product Bundles

Product Configuration

Consumption Period in License/Features

Time-Limited vs Subscription Licenses

License Types

Activations & Device Transfers

Features

Floating Features

Custom Fields

License Start Date

License Note

Maintenance Period

Trial Licenses

Cloud Concurrent Licensing

Floating License Server

Floating Licenses

Online License Activation

Offline License Activation

Air-Gapped License Activation

License Activation Types

License Entitlements

Reseller & Distributor Portals

The License Manager

End-User Portal

Offline Portal

Air-Gapped Portal

Portals

Signature

Signature Verification

License API Authorization

License Activation

License Deactivation

License Activation Offline

License Deactivation Offline

License Activation/Deactivation

License Check

License Feature Check

Adding Consumption

Adding  Feature Consumption

Consumption

License

Floating

Trial Key

Product Details

Get Device Variables

Track Device Variables

Device Variables

Changing Password

Versions

Installation File

Customer License Users

SSO URL

License API

Making API Requests

Management API Authorization

Retrieve Customer

Create Customer

List Customers

Update Customer

Delete Customer

Merge Customers

Export Customers

Import Customers from CSV

/customer-accounts/

/customers-import-results/

/clables/

Customer

List Products

Retrieve Product

List Bundles for a Product

List Products in a Bundle

/product-features/

/product-custom-fields/

/installation-files/

Product

List Orders

Retrieve Order

Remove Manager from Order

Add Manager to Order

List Managers on Order

Export Orders

Export Order

Generate License

Delete Order

Update Order

Change Customer on Order

Create Order

Order

List Licenses

Retrieve License

Update License

Update Licenses (Bulk)

Update License Product Features

Delete License

Check License

Change Order on License

Enable License

Reset License

Reset Consumptions on License

Disable License

Disable Licenses (Bulk)

Assign User to License

Assign Users (Bulk) to License

Set Activations Data for User

Unassign User from License

Import Licenses From CSV

Import License Features From CSV

Export Licenses History

/license-custom-fields/

/license-users/

/license-import-results/

/license-features-import-results/

/license-histories/

/license-activation-histories/

List Devices

Retrieve Device

Reset Device

Blacklist Device

Borrow Device

Release Borrowed Device

/device-variables/

Device

List Activities

/activities-hourly/

Management API

Getting Started

Best Practices

Advanced Usage

Licensing Scenarios

Tutorials

.NET/C# SDK

.NET/C# Management SDK

SDK Distribution and Licensing

C++ SDK

Java Modules

Java Hardware (Device) IDs

Javadoc & Downloads

Java Advanced Usage

Java SDK

Python Hardware (Device) IDs

API Client Usage Examples

Python Changelog

Python SDK

Common

Go License Client

Management Client

Go Changelog

Go SDK

Delphi SDK

Swift/Objective-C SDK

SDK Initialization

LicenseManager

License & License Data Objects

Java Exception Handling

Download Android SDK

Android SDK

Unity SDK

Errors and Response Codes

SDKs

config

license

registration

consumption

API Reference

Executable

Kubernetes (Helm)

Deployment

Floating Server

.NET/C#

Watchdogs

If I set up the watchdog timer each time I run a command in my program is it using the same instance internally, recreating, or adding a completely new timer with duplicate callbacks?

If I use the watchdog timer for floating and non-floating licenses, is there any need for me to call license.Check (online), since it seems like internally the timer is checking online and will throw all exceptions?

license.Register and license.Check

Do 'license.Register' and license.Check have same functionality?