Software Deployment

hi flakes

if you are running a vb script on uninstall

then use CALL VB SCRIPT FROM INSTALLATION

LOCATION Normal Execute Immediate/deferred.

CONDITION REMOVE="ALL"

SCRIPT FILE : browse to vbs file

script fucntion call : leave blank

test your script first to make sure it works and I think the CA will work fine

if you are still having problems let us know and then can show you how to do it in orca

Thanks Cygan,

I tried putting the action just before the InstallFinalize, but I dont see the action being run.I am writing to a log file to see if the commands are being run.But dont see the log file if i put the action before install finalize or after installfinalize.

Let me expand on what I am trying to do:

1.During install check to see if a registry key is there, if not, run four commands invoving two exe's within the installation .And also a regwrite .I have put this after InstallFinanize and its working fine, I can see the log being written,the registry entry is also there.I have given the condition as 'NOT Installed'.

2.During Uninstall check to see if a registry key is there, if yes, run four commands invoving two exe's within the installation,and also a regdelete .I have put this just before InstallFinanize and , I can see the log being written.But the app is still there in the add/remove programs section and no files are being removed.I have given the condition as 'REMOVE~="All"'.

I am obviously confused. :-) . Could you tell me where I am going wrong, and how can I do this using ORCA ?

Thanks for your time.

hi flakes

have you tested your scripts manually to make sure that they are working fine before you add them to the CA

the condition that you want for the install is REMOVE<> "ALL"
uninstall REMOVE="ALL"

my mistake sequence the uninstall after InstallValidate action just before installfinalize

Hi Cygan,


I have tested the scripts manually ,and they do work.

Now I am trying to break this up and try the embedded script way.

Thanks .

Hi Flakes,
have you altered your scripts to comply with the Installer Rules? See:
http://msdn2.microsoft.com/en-gb/library/aa371538.aspx
http://msdn2.microsoft.com/en-gb/library/aa372865.aspx
Especially, you have to make sure, that you don't have "WScript.CreateObject" call in them (Instead simply use "CreateObject").
Hope this helps.
Regards, Nick

Thanks nheim, I did have some "Wscript....." in there. Changed it now.

Thanks cygan , you were right, i did have something wrong in my original script. Now its okay.

One more question along the same lines :

Is there some way I can achieve all this using standard actions ? I have never used standard actions before. Any pointers to some examples/tutorials please ?

Hi Flakes,
what is your script doing exactly? We need to know that, before we could make any suggestions.
You where writing about deleting reg keys. This can be achieved with entries to the 'RemoveRegistry' table.
Hope this helps.
Regards, Nick

Nick,

This is what my MSi is supposed to do:

1.During install, check to see if a registry key is there, if not, run four commands invoving two exe's within the installation .And also a regwrite

2.During Uninstall, check to see if a registry key is there, if yes, run four commands invoving two exe's within the installation,and also a regdelete

can standard action do this ?

Thanks.

Hi Flakes,
yes this should be possible with built in MSI technics.
To find the registry key, use a RegLocator/AppSearch entry. This populates a public property with the reg key.
For the jobs to be done:
1. Put the regwrites in 1 component and set a condition in the components table with the property from AppSearch.
2. To call the exe's, you still need a CA, set a condition in the InstallExecuteSequence table with the Appsearch property and 'NOT Installed'

Hope this point you in the right direction.
Regards, Nick

Hi Nick,

Thanks for the quick reply.

Let me give it a try.

Thanks again for your time.

Hi Nick,

It's working fine.

Thanks a heap, you taught me something new.

[:)]

Hi Flakes,
good to read, it worked for you.
Keep MSIing :-)
Regards, Nick