Setting Module Retargetable Folder

[MobileMark II]

I'm using a merge module created in Visual Studio 2005. In VS, if I create an MSI incorporating my merge module, it sets the 'Module Retargetable Folder' to whatever I configure during setup (running the msi). Using IA, it uses 'Mdoule Retargetable Folder' as a literal part of the path. Is there a way to get IA to substitute 'Moduel Retargetable Folder' for the path selected during setup?

Desired: C:\\Program Files\\MyCompany\\MyApp
Actual: C:\\Program Files\\My Company\\Module Retargetable Folder\\MyApp

This causes the installation to fail - seemingly when IA attempts to set the desktop shortcuts. The failure results in the install being rolled back.

[sinan]

I believe you should be able to edit the MSM file to code in your desired path using Orca. Unfortunately the IDE does not have native support for configuring retargetable folders at this time.

What MSM is this?

[MobileMark II]

This is a MSM produced with the RTM of Visual Studio 2005.

[MobileMark II]

Does InstallAware support the insallation of merge modules created in Visual Studio 2005? When I try to install a setup that contains a single merge module, I receive the following error message:

Error:

InstallUtilLib.dll: Unknown Error

This seems to happen as the install is attempting to update the desktop shorcuts. All application files have been insalled, albeit one level too deep (in the \\Module Retargetable Folder\\), the base registry paths are set, but no keys are written, shorcuts are created on the desktop but the icon is not set and the shorcut paths are incomplete (missing the exe name).

Is this something I can resolve easily? I'm so close...

[sinan]

InstallAware works fine with merge modules - no reports of problems so far. For instance, users are merging Crystal modules, etc...I really do not know why you are having problems. Have you tested the MSM with other MSI files to see if the problem is in InstallAware or the MSM itself?

If you are also making the MSM yourself (that is, you know what goes where and what it installs), I'd encourage you to use InstallAware directly to install the files, registry keys, etc.; this is more flexible, you can leverage the power of web media blocks, and overall its easier and more efficient.

[MobileMark II]

I'm getting farther...

I'm guessing the culprit is the Custom Actions supported by Visual Studio Setup projects? Under Visual Studio 2005, it is now possible to create custom action dlls that are associated with the merge modules being built in VS. These Dlls allow pre and post processing to occur. If I remove these, the merge modules go off without a hitch. Now all I need to do is figure out a different way to implement the custom action functionality.

Thanks for all your help. You guys have been great and very responsive.

[sinan]

Thanks Please help spread the word

[MobileMark II]

No question. I've worked in the software industry for quite some time (for some large vendors) and have watched as ISVs continue to do away with "non profitable" services (like support). It's refreshing to find a software company that still focuses on customer support/satisfaction and quickly responds to questions and issues. It's almost like you care You've sold me! Now, if I can just find that discount coupon...

Keep up the good work!