File Menu
New
Create a new project file
Open
Open an existing project file
Save Project
Save the current project
Save Project As
Saves a copy of the current project
Tools Menu
Build project
Launch protection with the current project parameters.
Activate dotNet Protector
Launch dotNet Protector activation wizard. After installation, dotNet Protector works in demonstration mode (all generated assemblies will have a 5 days execution limit).
If you acquired a licence for dotNet Protector, you will have to activate it (see the Activation section).
The product key you will enter during activation will determine available features (dotNet Protector Edition : Classic, Professional or Advanced).
Re-check License
If your copy of dotNet Protector is activated, but the title bar indicates (locked), this means that dotNet Protector does not recognize any more the hardware associated with your license. This option makes it possible to start again the verification.
Import /Export License File
Allows to save / restore your licence file If you must reinstall your computer, save your licence file before un-installation; you will then be able to re-import and avoid activating once again. This option will work only if the material on which the license is imported is the same one as that on which it was exported.
This option is also useful if you chose the USB Key activation. You can then export to import your license file after activation, and import it on all the computers where you wish to run dotNet Protector (dotNet Protector will run only if the activated key USB is present).
This option is valid also for the ‘instant activation’ mode. In this mode, a license token is requested from each run of dotNet Protector. This token is associated with the computer that requested it. Computer-token association is deleted every 24h, which enables you to change computer each day. You must have access to Internet to run dotNet Protector in this mode.
De-Activate dotNet Protector
Remove the license file and erases the hardware hash on our activation servers. This option will enable you to activate another computer (hardware change). A de-activation key will be required; this key is not your product key. If you did not receive the de-activation key during activation or if you lost it, your license file will be removed, but hardware association will remain on our activation servers; you will not be able to activate another computer. If this case were to arrive, send an email to dotnetprotector@pvlog.com by specifying your license number; we will then do the de-activation manually.
Import Keyset
dotNet Protector activation process uses public/private key pairs and a symmetrical key. The key set contains all these keys. If you do not use the activation features (hardware lock) the key set is not fundamental. If on the contrary you activate this functionality, you must make sure that your program is protected with the same key set as your tool that delivers the licenses. The key set determines the encoding of product keys, configuration strings and license keys. It guarantees to you that one will not be able to generate product keys licenses, unless one has your private keys. Of course, the protected program only embeds the public keys. A key set is generated during the first dotNet Protector run. The generation of this key set relies on a cryptographic random generator to have the best uniqueness garantee.
Export Keyset
Allows you to save your key set.