You have to integrate TurboActivate within your applications. We have articles on how to do that. See Using TurboActivate.
Hi!
First of all, congratulations for you great software 😉
We're working in a custom program installer, using inno setup.
We have integrated LimeLM & TurboActivate without any problem, and the setup program checks the key as it's supposed to do.
The problem appears when, once installed , we have one .net application, and another flash application (both are the core of our product). If they're copied from the "validated" pc, into another one, they can be executed, without any key validation.
What do we have to do? We have to apply turboactivate into the final flash and .net applications, instead of the setup one?
Thanks for your help (and sorry for my bad english, Spanish are not famous for our english hehehe)
You have to integrate TurboActivate within your applications. We have articles on how to do that. See Using TurboActivate.
Thanks for your soon answer Sam.
What I don't have clear is that if I use TurboActivate within my apps....would I need one different key for each product (I mean, one for the installer, one for the .net app and another one for the flash app) , or will they work with the same one? It could be tedious for my final client if he has to enter three different passwords...(by the way, if that's the only choice, it's better than getting your product copied for no money...)
Thanks again
You can use the same product key for all your products if that's how you want to handle it. Also, if you go that route, if the user enters the product key and activates in the installer they don't have to re-enter the key in your other apps. TurboActivate takes care of all that.
Does that make sense?