Need help with a Basic Custom Action Installshield
Hi all
I am a packaging Newbie. I have been only packaging now for a grand total of 3 months. I took my training IS training back in December in the UK.
So far I have gotten off easy, just basic repackaging. However I am now required to do something a little more advanced, I need to create a custom action (something my professor told us to avoid doing). I have completely forgotten what to do. I have my basic *.ISM, what I need is to create a custom action that will copy 12 files (they are updated .dlls) that are not part of the msi into the install directory. So basically my msi will install the program then copy these dll files into the default directory. Thats it.
I know this is very basic operation, but I am a beginner and am truly stumped. I am using IS 2009.
Can anyone get me started of what I need to do? Is there a guide or something?
A Million Thanks.
I am a packaging Newbie. I have been only packaging now for a grand total of 3 months. I took my training IS training back in December in the UK.
So far I have gotten off easy, just basic repackaging. However I am now required to do something a little more advanced, I need to create a custom action (something my professor told us to avoid doing). I have completely forgotten what to do. I have my basic *.ISM, what I need is to create a custom action that will copy 12 files (they are updated .dlls) that are not part of the msi into the install directory. So basically my msi will install the program then copy these dll files into the default directory. Thats it.
I know this is very basic operation, but I am a beginner and am truly stumped. I am using IS 2009.
Can anyone get me started of what I need to do? Is there a guide or something?
A Million Thanks.
0 Comments
[ + ] Show comments
Answers (8)
Please log in to answer
Posted by:
langa100
13 years ago
Why create a Custom Action for this ? Why not just added the files into the MSI (if it is your MSI ) if not then create a transform that adds the files in?
Posted by:
mmarsh
13 years ago
Its not our *.msi, its from a manufacture who is using a legacy installer. So it has to be repackaged as a *.msi then patched with these bloody *.dll files.
Posted by:
Rheuvel
13 years ago
So, you're repackaging from legacy to MSI.... Which will get you your own custom MSI. There's nothing wrong with adding the DLL's to the MSI in that case, as langa100 was saying.
You could have done it while snapshotting, just copy/register/install the DLL's after you installed the application and before you make you end snapshot. That way they would have been included in your own MSI package already.
And if it isn't too much work afterwards, simply open the MSI with IS and add the DLL's to the right directory.
There's really no need at all for a Custom Action.
You could have done it while snapshotting, just copy/register/install the DLL's after you installed the application and before you make you end snapshot. That way they would have been included in your own MSI package already.
And if it isn't too much work afterwards, simply open the MSI with IS and add the DLL's to the right directory.
There's really no need at all for a Custom Action.
Posted by:
kardock
13 years ago
repackaging an msi file is a really bad idea. you'll get troubles.
take the vendor msi and create a transform for it.
just my advice!
take the vendor msi and create a transform for it.
just my advice!
Posted by:
anonymous_9363
13 years ago
@kardock: read the posts carefully. Remember that English may not be the OP's first language.
Posted by:
kardock
13 years ago
VBScab, i don't get it. the poster says it's not his msi, but a legacy installer. in it's first post, he's mentionning an original msi. so why not doing like usuall and extract the msi from the setup, then create a transform?
thanks!
thanks!
Posted by:
mmarsh
13 years ago
Kardock
I might have explained it badly. VSCAB is correct. The installer was a *.EXE which I repackaged into a *.MSI. I thought I needed to use a custom action to copy the updated files into the install directory once my MSI finished installing, but in fact I did as Reuval suggested which was to add the files in between snapshots, this solved my problem.
It turns out I did need to create a custom action in order to set permissions (as the user neglected to tell me this when I made my original msi), but all is well. I may ask about this at a later date.
Anyway package the is Done,
TO ALL: Thanks so much for your help! I am sure Ill be begging for more of it later on!
I might have explained it badly. VSCAB is correct. The installer was a *.EXE which I repackaged into a *.MSI. I thought I needed to use a custom action to copy the updated files into the install directory once my MSI finished installing, but in fact I did as Reuval suggested which was to add the files in between snapshots, this solved my problem.
It turns out I did need to create a custom action in order to set permissions (as the user neglected to tell me this when I made my original msi), but all is well. I may ask about this at a later date.
Anyway package the is Done,
TO ALL: Thanks so much for your help! I am sure Ill be begging for more of it later on!
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.