I have a product that is shipped on a CD-Rom containing a .MSI file created with a Visual Studio 2010 Deployment Project. I am looking for a way to control the number of times our software package can be installed. That is, if we sell the customer 15 licenses I only want the install process to work 15 times. On the same note, we need a way to allow the product to be reinstalled when hardware changes and software is upgraded.

I am open to using a dongle or some type of physical or software device. How are people handling these sorts of issues?

Thanks,

Tony
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
I don't think this kind of thing belongs in the installer but in the application. There was quite a good registration/serial number "shell" written in VB6 posted ages ago on Planet Source Code which you may be able to adapt, depending on which is your coding language. Nowadays, I think most of these things "phone home" to check whether or not the license is valid.
Answered 11/22/2011 by: VBScab
Red Belt

Please log in to comment
0
ORIGINAL: taiken

I am open to using a dongle or some type of physical or software device. How are people handling these sorts of issues?


SafeNet Sentinel HASP? You can control runtime access via individual local dongles or via a network dongle (concurrent). Pass along the costs to the customer.
Answered 12/01/2011 by: mazessj
Blue Belt

Please log in to comment
0
license server
Answered 12/01/2011 by: jmaclaurin
Third Degree Blue Belt

Please log in to comment
Answer this question or Comment on this question for clarity