AVAX Vector .NET v.3 - developer and runtime licensing =================================================== DEVELOPER ACTIVATION Activate the SDK on each development computer using RegAVAX.exe from the installation folder or the control's Developer activation... command in the Visual Studio designer. An internet connection is required for activation and deactivation. The number of development computers is determined by your license. Use the same issued v3 serial number for developer activation and the runtime Unlock call in your application. One developer activation covers both the x86 and x64 controls on that computer. Activation is required when using the designer or running/debugging the application in Visual Studio. Opening a form containing an unactivated control offers activation. Cancel leaves the control available in DEMO mode. To purchase a serial: https://store.gardos-software.com/en/product/avax-vector-net Before moving your developer license to another computer, use RegAVAX.exe or Developer deactivation... on the activated computer to release its seat. Use the Windows account with which you activated the SDK. RUNTIME USE IN YOUR APPLICATION Call Avax.cAvax.Unlock with your issued v3 serial number on each application launch, before InitializeComponent or any other creation of AVAX controls. Developer activation does not replace this call. VB.NET, in the startup form: Public Sub New() MyBase.New() If Not Avax.cAvax.Unlock("YOUR-SERIAL-NUMBER") Then Throw New System.InvalidOperationException("Invalid AVAX v.3 SN.") End If InitializeComponent() End Sub C#: public MainForm() { if (!Avax.cAvax.Unlock("YOUR-SERIAL-NUMBER")) throw new System.InvalidOperationException("Invalid AVAX v.3 SN."); InitializeComponent(); } Replace YOUR-SERIAL-NUMBER with your issued AVAX Vector .NET v.3 serial. Unlock returns True when the serial is valid. While developing, the computer must also be activated with the same serial to leave DEMO mode. Invalid, empty and v.1/v.2 serial numbers are not accepted. Alternatively, set drawing.UserSerialNumber = "YOUR-SERIAL-NUMBER" before StartAvax() to license that control alone. Assign this property in code; it is not shown or saved by the designer. Assigning an empty or invalid value leaves that control in DEMO mode. See Examples\RuntimeLicense.vb in the SDK installation, or RuntimeLicense.vb in the installed examples folder, for a complete form example. DISTRIBUTING YOUR APPLICATION Customer applications using a valid runtime Unlock call do not require developer activation on the customer's computer. Normal customer launches work without contacting the activation service and do not consume developer seats. You do not need to ship RegAVAX.exe with your customer application. Use the control DLL that matches your application's architecture: x86: bin\x86\Gardos-Software.Avax.x86.v3.dll x64: bin\x64\Gardos-Software.Avax.x64.v3.dll Include all managed dependencies from that same bin folder and its matching native SkiaSharp subfolder (x86\libSkiaSharp.dll or x64\libSkiaSharp.dll), plus ThirdPartyNotices.txt and Licenses. Do not mix x86 and x64 control DLLs in one application. The examples use matching files from Lib\x86 or Lib\x64. DEMO MODE Without the required license, the control remains in DEMO mode: - The drawing canvas displays "Not Registered - Avax Vector .NET". - Printed drawings, previews, captures, clipboard images and exported files include a registration label. - An evaluation notice appears when the first DEMO control becomes visible. The registration label does not change the editable drawing or undo history. An activated developer must still include the runtime Unlock call when distributing an application. The SDK license is separate from AVAX-CAD R3. SETUP AND UNINSTALL The SDK installs by default under: C:\Program Files (x86)\Gardos Software\AVAX Vector .NET v.3\ Setup requires administrator permission for this installation. It can activate a supplied serial without opening the registration window. If activation fails, the control remains in DEMO; use RegAVAX.exe to retry. Uninstall using Windows Installed apps and follow the uninstall wizard. Uninstall attempts to release the developer seat before removing the SDK. If deactivation fails, removal continues. You can retry deactivation with RegAVAX when available, or contact support for help releasing the seat. User-edited examples in Documents are preserved.