We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

Royal Indicator
Posts: 1
Joined: Mon Oct 02, 2006 9:58 pm

Expiration Option

Dears

I used Advanced Installer, and it is perfect, but it need Expiration Option.

I create my installer and I need Expiration Option to make my program trail and expire after one week or one month, and i did not find this feature in Advanced Installer.
gigi
Posts: 2103
Joined: Tue Apr 11, 2006 9:55 am
Contact: Website

Hi,

Advanced Installer does not currently support this feature. But we shall consider to implement it in a future release thank you for your suggestion. We add this on our TODO list.

Regards,
Gigi
________________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com
rwatson
Posts: 17
Joined: Fri Nov 10, 2006 11:34 pm
Location: Oregon

Couldn't this be done as a launch condition? I noticed in trying to make a new launch condition, I can use the Insert Operand panel (and the Property button) to get a Date property (I'm assuming this is the date the system is set to). Can't this be compared and an expiration message be presented? (I've tried this and haven't been able to format a date correctly that or else it definately isn't supposed to be a a string - can you help with that?)

Alternatively, couldn't a Custom Action be created on the Install event to fail the install if the system date was outside the intended range?
gigi
Posts: 2103
Joined: Tue Apr 11, 2006 9:55 am
Contact: Website

Hi,

The "Date" property returns the date of the system in a format depending on "Regional and Language Options" are currently set on the target computer. Thats why you can not compare it with a constant string.
Alternatively, couldn't a Custom Action be created on the Install event to fail the install if the system date was outside the intended range?
Yes you can create a DLL custom action. To abort the installation if a condition is not meet your DLL function must return ERROR_INSTALL_FAILURE code. As an example on how to create a custom action DLL please see:
http://www.advancedinstaller.com/user-g ... n-dll.html

Hope this helps.

Kind Regards,
Gigi
______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com
rwatson
Posts: 17
Joined: Fri Nov 10, 2006 11:34 pm
Location: Oregon

Thank you.

I went ahead and created a DLL in Delphi 7 (using JwaMsi and JwaMsiQuery, in case someone is trying to do the same). For this I used an EXPIREMONTH and EXPIREYEAR property in the installation. These I acquired like in your demo using MsiGetProperty().

If the program appears to have expired, I show a modal dialog box. While this can be rather easily circumvented (by changing the MSI tables), it is more of a warning step then anything else (aka the application should check this as well).

I returned ERROR_INSTALL_FAILURE if the program had expired.

Return to “Feature Requests”