Creating an MST to modify extension ownership
I want to deploy 7-Zip but the problem is that by default it does not take over any of the file extension which it supports, thus I am creating an MST which will do this during installation.
Thing is, I'm not sure of the best way to approach this. Can I do this natively in the MST or should I be calling an external script?
I've been trying to Google the subject, but I'm unsure what the correct terminology is for taking over a file extension.
Thing is, I'm not sure of the best way to approach this. Can I do this natively in the MST or should I be calling an external script?
I've been trying to Google the subject, but I'm unsure what the correct terminology is for taking over a file extension.
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
anonymous_9363
14 years ago
By far and away the simplest route is to capture the changes made when you select the new association. What tool are you using for capture?
Posted by:
Quitch
14 years ago
I'm not, 7-Zip is provided as an MSI, I'm just using InstaEdit to try and setup an MST to handle the file associations. Knowing which registry entries to change isn't an issue, I'm just unsure of the best way to set these to happen using an MST.
Posted by:
anonymous_9363
14 years ago
For Windows Installer, making file associations via registry entries isn't recommended, as file association can be an advertising entry-point. However, if you have no need for those, use the Registry table.
By "capture", I mean any means to capture the changes made. That could include a snapshot tool such as InstallWatch.
By "capture", I mean any means to capture the changes made. That could include a snapshot tool such as InstallWatch.
Posted by:
Quitch
14 years ago
So as a best practice I would need a capture tool? I've used them before, but that's such a resource sucking route.
Posted by:
anonymous_9363
14 years ago
Best practise?!? Who cares? I find a lightweight snapshot tool indispensible. I used to use In Control but have switched to InstallWatch. It's a simple install and, as I say, lightweight and belongs on your packaging machine for QAD snaps.
Posted by:
Quitch
14 years ago
Packaging machine? You overestimate my company ;)
I'm looking at the tool but I don't understand the difference between InstallWatch and InstallRite.
I'm looking at the tool but I don't understand the difference between InstallWatch and InstallRite.
Posted by:
anonymous_9363
14 years ago
Packaging machine? You overestimate my company ;)You can't package properly without a dedicated "machine". At the very least, have them spring for a gob of memory, then install Virtual PC or VirtualBox, both free.
I'm looking at the tool but I don't understand the difference between InstallWatch and InstallRite.I use InstallWatch. As above, if you have VMs/VPCs/VirtualBoxes, you could install both. If you don't like one, ditch the VM with it on.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.