/build/static/layout/Breadcrumb_cap_w.png

license in mst file

Hi!

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   [ + ] Show comments

Answers (5)

Posted by: anonymous_9363 14 years ago
Red Belt
0
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?
Posted by: lanselots 14 years ago
Fifth Degree Brown Belt
0
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:
CheckForLocalhost
CheckForSpaces
CheckForSpaces1
CheckForSpacesDir
DeleteSettingFiles
InstallSqlExpress2005
UpgradeOff
UpgradeOn

And some dll:
WiseSingleFileCheck
WiseUpgradeCheck
WiseUpgradeCheckEx

also, i`m not shure that it will help you, taht i put those custom action names
Posted by: mekaywe 14 years ago
Brown Belt
0
Did you import the registry into the Feature which gets installed?
Posted by: shweta_kar 14 years ago
Blue Belt
0
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.
Posted by: anonymous_9363 14 years ago
Red Belt
0
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!
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ