This article is for the Super Dog, and the toolkit version of the Super Dog Kit is 2.4 version. The Super Dog pictures are as follows:
It consists of two dogs, one is a super dog and the other is a development dog, which is required in this blog post. First, install the development suite on the CD.
The next step is to demonstrate the authorization additions for a simple C # generated program.
The sample folders are as follows:
This is a simple program that uses C # development to complete and is currently ready to run directly, then we shut it down and run the development Dog Suite.
We want to achieve a what kind of function, this software we distribute out, do not want others casually copy run, of course, can also use the binding computer's serial number, but in this case, the distributed software can only be run on a certain computer, and security is not very high.
Now you can bind a super dog, others can take the super dog can let the software run on different computers, and no super dog will not be able to copy run.
Then choose to use the official development number and click Add Program to select that exe file:
Then select the program you just added and click the Protection Settings button below.
Then select the output directory and file again. Easy to find files. Then click on the Protection button below, waiting to complete, you can go to the file directory you just selected to find the file.
Copy all the files to the previous demo folder and overwrite them. When you have a super dog, it works.
If there is no super dog, there is no version open program, immediately you open the program, then the dog pulled out, after a few minutes this program will also prompt no super dog, has been playing windows.
The above scenario is for an authorization, permanent use mechanism, suppose I need to issue a trial period of 30 days of software, what should we do? Or choose from the Developer Toolkit interface
Then click Add License:
Then we see four different license types, and the following actions are consistent, so here we have the number of executions as an example, assuming that only the program is allowed to execute 5 times, then
After the feature is written to the Super dog, then proceed to the beginning of the process until the protector is set up.
Then replace the generated file with the EXE, then try to run it 6 times to see.
Then the frame is not kept, and the feature has failed. The mechanism by date is almost the same as this one. Don't dwell on it.
I believe there is a clear concept here.
C # Crypto Dog Super Dog Cryptographic Program Authorization Sample program authorization verification