Disadvantages of using Custom actions in MSI
What are the disadvantages of using custom actions in MSI? or Why use of Custom Actions is not a part of best practices? in most of the interviews, this question is being asked.....what can be the perfect answer?
0 Comments
[ + ] Show comments
Answers (10)
Please log in to answer
Posted by:
Inabus
15 years ago
Posted by:
suchi.jigar
15 years ago
Posted by:
anonymous_9363
15 years ago
The answer is that it depends on what the CA is doing.
In *most* cases, CAs are used as a port of last resort, to perform a task which WI can't do natively. For CAs which call script, there's the maintainability/documentation angle to be considered. That might be looked on a disadvantage.
For CAs which call DLL functions, the DLL has either to be present or stored in the Binary table. I guess the former requirement (meaning that the package has a dependency - think InstallShield-driven packages, for example) might be considered a disadvantage by some. Even that can be catered for, though, with the use of AppSearch/LaunchCondition.
Other than that, I really can't think why anyone would regard the use of CAs as a disadvantage. To my mind, it's a stupid question but that's probably NOT the answer to give at an interview LOL.
In *most* cases, CAs are used as a port of last resort, to perform a task which WI can't do natively. For CAs which call script, there's the maintainability/documentation angle to be considered. That might be looked on a disadvantage.
For CAs which call DLL functions, the DLL has either to be present or stored in the Binary table. I guess the former requirement (meaning that the package has a dependency - think InstallShield-driven packages, for example) might be considered a disadvantage by some. Even that can be catered for, though, with the use of AppSearch/LaunchCondition.
Other than that, I really can't think why anyone would regard the use of CAs as a disadvantage. To my mind, it's a stupid question but that's probably NOT the answer to give at an interview LOL.
Posted by:
dj_xest
15 years ago
Posted by:
dj_xest
15 years ago
Posted by:
Inabus
15 years ago
Posted by:
dj_xest
15 years ago
Posted by:
cygan
15 years ago
What are the disadvantages of using custom actions in MSI? or Why use of Custom Actions is not a part of best practices? in most of the interviews, this question is being asked.....what can be the perfect answer?
what are CA's ?
answer - they enable us to add specialized functionality to our msi's which we certainly cannot do with the msi technology
when we run CA's we are taking windows installer out of the question.
if you had entries in the host file that you wanted to add to your msi
will you be adding the host file to the file table, certainly not
a vbscript will do the trick
what about this
lets say what are the limitations of msi technology and why use custom actions instead
Comments:
-
Custom actions exist, as has already been mentioned, to provide functionality that the native MSI installer does not have. It is also a useful alternative to having a full blown MSI editor, as it means that you can add things like configuration files without having to add actual files - for example it is really easy to write a vbscript that generates a configuration file and add it to the binary, custom action, and InstallExecute sequences and not have to worry about generating additional CAB files or recompiling. Yes, you need to think about the install, uninstall, repair and rollback scenarios but generally these are simple problems with simple solutions. - EdT 10 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.