Contents 

Introduction
Welcome
System Requirements
Graphical User Interface
Overview
Main Panel
Menu/Bar Items
GUI Elements
Assembly List
Assembly Properties
License File Name
License Generator
License Information
Lock Settings
Master Key
Protection Settings
Licensing System
Understanding The License System
Hardware ID
Hardware Lock
License File
Locks
Master Key
SDK
General Information
IntelliLock.Licensing.dll
IntelliLock.LicenseManager.dll
IntelliLockDB.dll & System.Data.SQLite.DLL
Definitions
Mapping File
Merge Assembly
Obfuscation
Pack Assembly
Tools
License Check
Hardware ID Check
Stack Trace Deobfuscator
License Reactivator
Testing
Library - Test Environment
Examples
Lock An Assembly
Unlock An Locked Assembly
Floating Licensing
Global
Intranet
Server Validation
License Server Validation
Ordering
Register Online
License Agreement
Why register?
Support and Contact
Technical Support
Contact
Command Line Parameters
Visual Studio Add-In

IntelliLock Online Help

Prev Page Next Page
Library Development — Test Environment
 

Library developers will often want to test their project output alternately under unprotected and IntelliLock locked/protected conditions. To alternate your test environment, first delete the existing reference to your library output in your test project and delete any library components installed to the Toolbox.
 
• To test the IntelliLock processed version of your library, re-add the reference to your library back into your test application, this time pointing the reference to the IntelliLock processed version of your library (Solution Explorer->References->Add Reference->[IntelliLock processed version of your library]). Install this IntelliLock processed version of your library as well to the Toolbox.
 
• To test the unprotected version of your library, add the reference to the unprotected version of your library into your test application, and install the (same) unprotected version of your library to the Toolbox.
 
In each case, the singular reference to your library and the version of your library installed to the Toolbox must be in agreement.