Merge Modules with Retargetable path - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

Activeplan
Posts: 9
Joined: Mon Apr 11, 2011 3:26 pm

Merge Modules with Retargetable path

I've recently been required to add a merge module that requires a retargetable folder path setting.
If I use Visual Studio to create an installer I can see a number of properties for this module including the retargetable one.

In Advanced Installer double clicking on the module returns a list of parameters that simply have GUIDs for their name:
msm.PNG
msm.PNG (51.59 KiB) Viewed 6223 times
This is making it very hard to know which property to set. Why doesn't AI use the property names like VS does? Luckily I only need the one and I do notice one entry has a value of [TARGETDIR] so I assume it is this one.
If I leave this as is the msm module files will be installed under <my application dir>/Module Retargetable Folder.
I require the files to be placed in <my application dir> or my app can't find the assembly.
I try setting [TARGETDIR] to [APPDIR] but then I get an error on installation startup stating the destination directory doesn't exist (of course not it hasn't created it yet so why is it checking it on startup?).

Any ideas on these issues?
Thanks.
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Merge Modules with Retargetable path

Hi,
In Advanced Installer double clicking on the module returns a list of parameters that simply have GUIDs for their name
Most likely these GUIDs were automatically generated when creating the MSM. Another possibility is that they were set by the MSM developer. Visual Studio shows less information because it offers less functionality compared to Advanced Installer.
Why doesn't AI use the property names like VS does?
How does Visual Studio show them? Can you provide a screen-shot? Also, can you please send us the MSM or a link to it to support at advancedinstaller dot com so we can investigate it?
If I leave this as is the msm module files will be installed under <my application dir>/Module Retargetable Folder.
I require the files to be placed in <my application dir> or my app can't find the assembly.
This is caused by the merge module configuration. It's parameters seem to be configured incorrectly.
I try setting [TARGETDIR] to [APPDIR] but then I get an error on installation startup stating the destination directory doesn't exist
Please note that merge module properties are used with the module GUID by a MSI. So in your MSI package you would set something like:

Code: Select all

TARGETDIR.<module_guid>
where "<module_guid>" is the MSM GUID.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Activeplan
Posts: 9
Joined: Mon Apr 11, 2011 3:26 pm

Re: Merge Modules with Retargetable path

Here's what VS shows:
properties.PNG
properties.PNG (17.04 KiB) Viewed 6217 times
I have sent a link to the MSM to you.

Thanks.
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Merge Modules with Retargetable path

Hi,

Visual Studio shows only one configurable parameter, your MSM file contains a lot more. Also, it resolves the parameter in a weird way because it's not a folder, it's actually the target of a custom action which sets the folder.

Basically, the MSM is configured in a strange and possibly incorrect way. Because it involves your folder structure, we should continue this discussion through email.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Activeplan
Posts: 9
Joined: Mon Apr 11, 2011 3:26 pm

Re: Merge Modules with Retargetable path

Thanks for the very detailed email you sent me.
I am now contacting the MSM suppliers support for further help.

10/10 for response time and the very helpful support!

Return to “Common Problems”