Hello dear freinds
I use a custom action in my project that itself is a installation package too.
(It's a installation for a camera.)
In general, this custom action run correctly, but my question is that when an old version of it is exist on target system, the custom action not run again.
How can I prevent from this?
Regards
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Intrusive Custom Action
Started by
sni63
, Oct 22 2008 13:20
4 replies to this topic
Posted 28 October 2008 - 23:50
You need to set a condition on your custom action.
If you dont want the action to run when an old version of the exists, then you code will need to check for this and set a condition accordingly, and then use this condition on the action.
If you dont want the action to run when an old version of the exists, then you code will need to check for this and set a condition accordingly, and then use this condition on the action.
Posted 30 October 2008 - 05:57
Thanks luke.
Now, how can I do that? Please.
May you explain that with an example my freind?
Now, how can I do that? Please.
May you explain that with an example my freind?
Posted 30 October 2008 - 06:40
I dont have an example piece of code but on each custom action, you can set conditions for it.
So you need to create a custom action that detects when you dont want this action to run and set a property. i.e. DONT_RUN_NEW_ACTION=1
Then place a condition DONT_RUN_NEW_ACTION!=1 on the first action.
So you need to create a custom action that detects when you dont want this action to run and set a property. i.e. DONT_RUN_NEW_ACTION=1
Then place a condition DONT_RUN_NEW_ACTION!=1 on the first action.
Posted 30 October 2008 - 09:46
Hi,
If you have a unique registry that is created when the driver is installed, then user AppSearch to search for that registry and assign a Property based on the result.
You can then execute your custom action based on the property.
Hope this helps.
-Vijay
If you have a unique registry that is created when the driver is installed, then user AppSearch to search for that registry and assign a Property based on the result.
You can then execute your custom action based on the property.
Hope this helps.
-Vijay