does any one met the problem with vendor msi, and the problem is that, i created mst file, installed it, captured, because i needed to import one license file, after that it creates registry, so i imported it in my mst file, and after installing transfoms i cheked that registry but it not there, also there is custom action some, and i cannot figured it out why it happened, and which custom action i need to modify, may be some one had something like that?
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


OK, transform first...

Did the verbose log you took of the install show that the transform was being applied?

Custom Action
It's not clear what it is you are asking. Can you clarify, please?
Answered 03/03/2010 by: VBScab
Red Belt

Please log in to comment
I also tryed to use repackaging for the exe file, but it didn`t work, i get the same result, where captured license file, after installing in registry is missing.

speaking about custom action, there is many vbscripts:

And some dll:

also, i`m not shure that it will help you, taht i put those custom action names
Answered 03/03/2010 by: lanselots
Fifth Degree Brown Belt

Please log in to comment
Did you import the registry into the Feature which gets installed?
Answered 03/04/2010 by: mekaywe
Brown Belt

Please log in to comment
Check the vbscript content and supress the appropriate Custom action one by one and check it whether the data gets deleted or not e.g the one mentioned DeleteSetting files Custom action.
But if it works , due to supressing the CA lot of other logic in the script will also not get executed.

Instead what you can do is, write a vb script to write those reg data and keep the sequence at the extreme end.
Answered 03/04/2010 by: shweta_kar
Blue Belt

Please log in to comment
Did you import the registry into the Feature which gets installed?Good point. If the component is attached to a feature which isn't selected for installation, it clearly won't get installed. I tend to create a separate feature for this type of thing and set it either hidden, to always be installed, or both, depending on how bright your target audience is. For vanilla users, go with both!
Answered 03/04/2010 by: VBScab
Red Belt

Please log in to comment