I have generated a custom action(Execute Program from path) [Wise Studio 7.0] to register the license key, it goes like this-- Execute Program From path 0 Command Line C:\Program Files\xxx\register.exe /Axxxxxx . & this worked fine on XP but not on Win7 , what change I need to do , to make it run on Win7 as well & Should be created in same package , Am I using the right custom action ?

Please Suggest ,

0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


I take it your Win 7 build is 32-bit? If not, your program files folder will be named slightly differently. If so, ensure that your CA is running as Deferred in a System Context. Probably somewhere between InstallFiles and InstallFinalize. Then consider using a slightly different approach to hard coding the path to register.exe - perhaps a different type of custom action such as a VBScript using an environment variable to get the 'Program Files' folder? Or if 'register.exe' is installed with the package, use a 'Execute Program from Installed Files' custom action instead....
Answered 10/26/2011 by: captain_planet
Black Belt

Please log in to comment
Thanks Captain_planet, my Win7 is 64bit, I have ran into an other situation , the package which I have created is working only on that XP machine not on any other XP machines, as I mentioned in my earlier post about the custom action, I have left the Property as default i.e., wisedebug mode, should I need to change this to something else moreover am using this CA in user sequence , Am I doing it right?

Please suggest,

Answered 10/26/2011 by: hrakeesh
Senior Yellow Belt

Please log in to comment
first captain_planet already told you what to do, i suggest you reread his answer. why ask the question if you don't even bother to read the answers given to you.

your path should be using a folder reference as opposed to a path from a property.

[$componentKey]register.exe or similar.

you also need to run the exe as deferred in system context. you may also find uac is blocking your attempts at running elevated "if" that is the case you can use elevate.exe to get around it. but it shouldn't be an issue in this situation.
Answered 10/26/2011 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment