Newbie help: Register DLL via MSI-package (Wise Package Studio)
Hi :)
I'd want some newbie help with creating an MSI-package using Wise Package Studio 5.5.
All I really want to do is:
1. Unregister any existing version of the specific DLL (regsvr32 /u name.dll)
2. Copy my new DLL to %WINDIR%.
3. Register my new DLL (regsvr32 name.dll)
I want this packaged as an MSI file for AD GPO-distribution.
Can anyone give me some pointers as to where I begin?
I'd want some newbie help with creating an MSI-package using Wise Package Studio 5.5.
All I really want to do is:
1. Unregister any existing version of the specific DLL (regsvr32 /u name.dll)
2. Copy my new DLL to %WINDIR%.
3. Register my new DLL (regsvr32 name.dll)
I want this packaged as an MSI file for AD GPO-distribution.
Can anyone give me some pointers as to where I begin?
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
nmi
19 years ago
Posted by:
masken
19 years ago
Posted by:
nmi
19 years ago
Ok, as you want it as an MSI you could do this but have a script which runs as a custom action to do what you need OR...
If you deploy your DLL as a file in your package it will be self registered, you may want to schedule your custom action before you deploy the files so that you can unregister any existing files although this may not be necessary.
Hope this helps.
nmi
If you deploy your DLL as a file in your package it will be self registered, you may want to schedule your custom action before you deploy the files so that you can unregister any existing files although this may not be necessary.
Hope this helps.
nmi
Posted by:
ab2cv
19 years ago
Posted by:
craig16229
19 years ago
masken,
If you are not completely comfortable with the above options, there is something else you might consider and test: a tool called CCRP Registration Utility. I have used it many times with problematic .tlb files. It can also register .ocx files.
There is info on it here:
http://itninja.com/link/drive-image-product-page2
You could run a separate capture of the changes the tool makes when it registers and unregisters your .dll files, and "add / update resources" in your existing .msi.
Craig --<>.
If you are not completely comfortable with the above options, there is something else you might consider and test: a tool called CCRP Registration Utility. I have used it many times with problematic .tlb files. It can also register .ocx files.
There is info on it here:
http://itninja.com/link/drive-image-product-page2
You could run a separate capture of the changes the tool makes when it registers and unregisters your .dll files, and "add / update resources" in your existing .msi.
Craig --<>.
Posted by:
masken
18 years ago
Posted by:
plangton
18 years ago
Hi Masken,
It can be done as an MSI, but I'd agree thats its probably not the best.
If you need to to run as an admin you can run the script using psexec (www.sysinternals.com) to run it as another user on the workstations.
If you are determined to go the MSI route, then its custom actions for unregistering, and Wise makes sure that DLL's/OCX's etc self register, but you can make it by right clicking on the file in the File view, selecting Properties (I think, I don't have it in front of me) and one of the tabs is for DLL registration.
Hope thats helped.
Rgds
Paul
It can be done as an MSI, but I'd agree thats its probably not the best.
If you need to to run as an admin you can run the script using psexec (www.sysinternals.com) to run it as another user on the workstations.
If you are determined to go the MSI route, then its custom actions for unregistering, and Wise makes sure that DLL's/OCX's etc self register, but you can make it by right clicking on the file in the File view, selecting Properties (I think, I don't have it in front of me) and one of the tabs is for DLL registration.
Hope thats helped.
Rgds
Paul
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.