1) What is the best way to attach registry entries to an existing component (when importing from a registry file)? When I import registry entries from a registry file, they are added as new components. I want to attach these registry entries to existing components. The only way I could figure how to do this is to import the registry entries (in the registry view), switch to the organization view, then drag/drop each registry entry to the component I want it attached to. This certainly isn't practical for hundreds/thousands of registry entries. It sounded like there was improvement in this area a few versions ago: http://www.advancedinstaller.com/forums ... =1&t=21456 , but I couldn't figure out a better way than the drag/drop method.
2) InstallShield has a feature "REG File To Merge At Build", where you can point to a registry file, and InstallShield will import the registry entries into the component at build time. Is there anything similar in AI? *Feature request*
3) I have the following setup, which is similar to a mixed 32/64 project, but I'm setting up everything manually.
Code: Select all
Media view:
Build32
Build64
Organization view:
FeatureA_32 (Included only in Build32)
ComponentA_32
App.exe (32bit)
FeatureA_64 (Included only in Build64)
ComponentA_64
App.exe (64bit)
4) Related to question 3, how do I handle COM/Interface/TypLib registry entries that also need to be added twice (32bit and 64bit)? COM registry entries are being added to the "COM" view (instead of the registry view), and it doesn't look like I can use the above method (http://www.advancedinstaller.com/user-g ... istry.html) in this view?
In the end, I'm trying to figure out how to best address my setup (as shown in question 3). I have 32bit and 64bit components that use the same registry entries (some of which will be COM/Interface/TypLib), but it doesn't seem like I can add the same registry entries to both components (at least, not very easily).
Thanks.
FOLLOW US
Get the latest news in Application Packaging