Our UWP licensing model has been changed. Since 2016 v2 release, each application that uses UWP Edition controls requires a unique license key (either evaluation one or fully licensed key) to be validated at runtime.

UWP Licensing Basics

In previous releases UWP Edition made license checks at design-time. If you had no valid license, it set C1NagScreen.Nag attribute in your xaml. Starting from 2016 v2 release this is obsolete. If you still have C1NagScreen.Nag attributes anywhere, you should remove them. Now UWP Edition uses runtime app-based licensing. Each application requires unique license key to be validated at runtime. Our licensing web service and Visual Studio Add-In build these keys based on your license and application name as it is set in your application's AssemblyTitle attribute. Make sure that you use correct name on the license generator web page.

Evaluation Keys

Evaluation keys are good for 30 days, and should not be distributed with published apps. You can get and renew evaluation key any time even if you have no valid license.

Fully Licensed Keys

Fully licensed keys never expire so long as your app uses a version of ComponentOne Studio UWP Edition, Studio Enterprise or Ultimate included with your subscription. You can update apps beyond your subscription end date so long as you continue to use a valid version of UWP Edition.

How to License Your App

Copy generated application key and insert it into beginning of you application class constructor:

sealed partial class App : Application  
{  
    ///   
    /// Initializes the singleton application object.  This is the first line of authored code  
    /// executed, and as such is the logical equivalent of main() or WinMain().  
    ///   
    public App()  
    {  
       C1.UWP.LicenseManager.Key = "";  

Grapecity License Manager Add-In

An alternative way of getting app key and inserting it into application is to use Grapecity License Manager Add-In. This Add-In creates GCDTLicenses.xml file with license key and inserts it into you application project as an embedded resource. Both C1.UWP.LicenseManager.Key set from code and key included into GCDTLicenses.xml file are valid and work in the same way. You can use the one which is more convenient for you. Note, if application sets C1.UWP.LicenseManager.Key from code, UWP Edition controls will ignore GCDTLicenses.xml file content.