HI, I wonder if my script change the system status(write registry enteries,change com+ configuration etc....) when running in a repair mode should i run the script? where is a good place to run the script?
what is the difference between a custom action and install script? why should i use install script and not a custom action with vb script?
If the information is missing from the system, it might be worth running during repair. (Keep in mind that writing registry keys and such is generally better left to built-in MSI actions, though.) In any case, an action that makes system changes should be scheduled in the Execute sequence during deferred execution.
In an MSI project, InstallScript is one of many ways to implement a custom action.
I am only using install script to update com+ application since I don’t believe IS nor WI support updating components while leaving the roles and configuration?!
