Code to handle licensing for Visual Basic 2008 -

Is there a license point that can be used for licensing for my Visual Basic 2008? some. Any recommendations on Net Reactor, where the person is required to enter the license key?

Thanks,

Kevin. Unfortunately, there are several possible licensing mechanisms I've used CrypKey () in the last one, but

I do not recommend it until it is true:

• You can (or create) a web site to perform the activation operation.
• You have a customer support number, which can make any call if web activation is not possible (for example, the user is behind the firewall).
• If you have time to troubleshoot problems (for example) the customer closes the service required for a license operation or changes the hardware.
• You are ready to wait for the new operating system to be released for the crawl.
• You are happy with a Windows-only solution

In addition to this, your questions are unclear to some extent. There are several possible changes to the subject of licensing. The safest software-only solution I know is a challenge-response type implemented by Cripchie, which is similar to Microsoft's product activation system. Sometimes you may want to include the "free trial" period. Some applications require "concurrent use" licensing and require a server process running on the customer's machine (or network). Some just use the codes recorded in the installation time (which specifically include an embedded serial number, so a particular installation key can be used more and more).

These days, I often do my own role. It is just that easy way to remember, the more complex you do it, the more likely it is that you want to get service calls due to it. Generally, I use a challenge-response type mechanism where the challenge part is either based on the safe hash of the user or machine information (for example the email address of the licensed user, the machine name) Types of safe one-way change (often using a public / private key pair)

Hope it helps.