Deploying TurboActivate.dat

Hey Martin,

1) Do you store activation details within this file?

No the activation details are stored separately.

2) If you re-deploy this file to a production user who has already activated and the file is overwritten - what happens? Do they lose they're activation details and need to re-activate?

Nope.

3) what is the purpose of the file if you don't store activation details inside it?

It contains things like your product name, company name, infromation needed to verify product keys, etc.

Tell me if this helps.

Cool thanks,

In the situation where we need to change the trial period for an existing client does redeploying the TurboActivate.dat accomplish this???

We have a situation with our dev machines where it no longer offers a trial period even after deactivation. I suspect this maybe to do with having an the trial period set to zero initially on the website. I've changed it to 3 days - so do I know need to download the .dat file again and overwrite existing deployed files on our dev machines.

This is all just for testing different scenarios so we don't get any surprises in production! 🙂

Thanks

In the situation where we need to change the trial period for an existing client does redeploying the TurboActivate.dat accomplish this???

Yes. But if you just want to extend the trial for a user then use trial extension: Timed trials in your app.

Hi,

This didn't really answer my question.

Why when I install onto a new machine does it not offer a trial period???

Please advise.

The trial length data is stored in the TurboActivate.dat. However delivering a new TurboActivate.dat with your app (with a longer trial length) does not necesarily increase the trial length (unless you're on a fresh computer).

Hence my mentioning trial extensions.

Does that make sense?

Yep, thanks!