After validating a license, get a TimeMonitor object. The TimeMonitor provides information about the state of a Time Limit. After obtaining a TimeMonitor you can use the exposed properties to query the state of the time limit.

var monitor = _license.GetTimeMonitor();
MessageBox.Show( 
    String.Format( "You have {0} of {1} remaining.", 
        monitor.TimeRemaining, 
        monitor.TotalTime ) );

After validating a license, get a UseMonitor object. The TimeMonitor provides information about the state of a Use Limit. After obtaining a UseMonitor you can use the exposed properties to query the state of the time limit.

_license = SecureLicenseManager.Validate( this, null, null );
var monitor = _license.GetUseMonitor();
MessageBox.Show( 
    String.Format( "You have {0} of {1} uses remaining.", 
        monitor.UseCount, 
        monitor.UseLimit.Uses ) );

Serial number masks are calculated by DeployLX when the license is edited in the DeployLX License Manager. As the license is modified and options changed, DeployLX will ask to recalculate the license masks. On occasion the serial numbers generated for the license will not match the masks. 

DeployLX Licensing supports a lightweight diagnostic mode that captures additional details and modifies behavior to make it easier during development to diagnose issues and test licenses.

In the previous post, I showed how to use the Session.Get<T> syntax against an arbitrary property on the entity. The primary limitation with that method is that it only works for constant values. The following will work with constants, local variables, return values from methods, etc.

While many of my entity classes use surrogate primary keys, they also have natural keys (Product SKU for example). When I want one of those entities it's more natural to use the natural key, naturally. Normally that requires a CreateCriteria call, I'd rather just call Get<T> like I can with the surrogate keys. So I created an extension method that lets me do this:

Being able to encorporate a veiling process into your MSBuild project is an easy way to veil as you develop. This can also be beneficial for testing, as you are not waiting until the end to begin your testing. 

Visual Studio 2008 offers a great suite of testing tools for developers. One of the the nicest things is the ability to generate reflection based accessor assemblies that let you access the private members of classes. There is still opendebate about the benefit of testing private methods but for some things -- especially security related -- where it makes a great deal of sense. Getting at those private methods however is not the easiest thing to do.

The Creating a Custom Limit topic in the Developers Guide describes how to create your own custom license limit. If you are using the embeddable C# runtime, you will need to make a few changes.