I am working on an installer that runs on both XP and Vista/Server 2008. XP works fine.
The problem on Vista is that I need to perform an action based on a user folder/filename
selection. I can't run this in the InstalllExecuteSequence because I must determine if the
user input is correct and possibly modify the UI sequence. Specifically, I need to test for the
presence or absence of a particular file.
I can't wait for InstallFinalize as that is too late.
However, a DoAction in the Next button of the UI causes a Vista permission abort.
I have to place the vbs script in the UICustomActions. The only option is "Immediate
Execution" and this does not allow the "Deferred with no impersonation" that
Vista seems to want.
Running the install as Admin works, but running as a user with Admin privileges does not!
Running as Admin also causes all installed files to be owned by admin and I have to
run another script at the end to change tthe owner and permissions! And I certainly
do NOT want to launch the application as Admin because the application will create
lots of additional files owned by Admin - what a mess!
Is there some way around this mess? How can I get Vista to simply run my scripts?
You have a great product
FOLLOW US
Get the latest news in Application Packaging