Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Software Protect Key

Status
Not open for further replies.

zalmey

MIS
Feb 6, 2002
15
PK
Hi All
Dears i want to protect my software using the dll file. How can i protect. I am a new bie. guide. :)
 
the simplest way would be to use the reg, have a standard key and test to see if it is in the reg

look at GetSetting SaveSetting

The key could be as simple as all numbers in a block have to add upto a number using the ascii key value of the char for the alphas

 
VB has some built in protection that you can use for ActiveX controls. Look in the index of the VB docs under "license".

I'm not sure if this is what you are looking for, but it might help get you started:

Licensing Issues for Controls

Licensing for controls is a sensitive issue. After you've spent hundreds of hours developing a control, what if somebody else puts an instance of it on a UserControl, exposes all the properties, methods, and events, adds one or two trivial properties, then compiles and sells it as a new control?

Visual Basic's licensing support protects your investment. When you add licensing support to your control component, a license key is compiled into it. This key covers all the controls in the component.

Running your Setup program transfers the license key to another computer's registry, allowing your controls to be used for development. Simply copying your .ocx file to another computer and registering it does not transfer the license key, so the controls cannot be used.

To add licensing support to your control project

On the Project menu, click <MyProject> Properties to open the Project Properties dialog box. Select the General tab, check Require License Key, then click OK.
When you make the .ocx file, Visual Basic will create a .vbl file containing the registry key for licensing your control component. When you use the Package and Deployment wizard to create a setup for your .ocx, the .vbl file is automatically included in the setup procedure.

 
zalmey --
This topic has been covered many times -- please do a search for "unique identifier", etc.

Chip H.


____________________________________________________________________
Click here to learn Ways to help with Tsunami Relief
If you want to get the best response to a question, please read FAQ222-2244 first
 
Dears
chiph i search the topic but i couldn't be able to find it. :)
 
A search on 'licensing' in this forum gives 61 results. On the first page there are several threads dealing with your problem.

faq222-2244 also gives guidance on basic research

________________________________________________________________
If you want to get the best response to a question, please check out FAQ222-2244 first

For tsunami relief donations

'If we're supposed to work in Hex, why have we only got A fingers?'

for steam enthusiasts
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top