InstallAware

Hi,

I use merge modules in my setup for ATL/CRT/MFC/STL7.1. If I turn "Always cache setup sources" on then the install fails because the merge module or it's file (eg: atl71.dll) isn't found in [ALLUSERS]Applicationdata\\...

I already found a thread that may be related:
http://www.installaware.com/forum/viewtopic.php?t=4685

How can I solve this problem? I need cache setup sources for my single file setup because of fututre patching.

Thank you!

I still need a solution for this.

I have to install Visual C++ Runtime 7.1. Runtimes are not available by IA so I have to take merge modules, but this also doesn't work with cache setup sources.

When the runtime for vc7.1 will be available?

I encountered the same issue with my installer, although in a much more specific scenario.
My installer is configured to:
- build a "Compressed Single Self-Installing EXE"
- "Always cache setup sources" checked
- install the Microsoft_VC90_CRT_x86.msm and Microsoft_VC90_MFC_x86.msm merge modules

When I build the installer from the IDE, my installer runs without errors.
When I build the installer from the command line (no parameters except the .mpr file), the installer fails at runtime with the error message "Error reading from file: C:\PROGRA~2\{CCCA5~1\Windows\winsxs\ulMFCx86\mfc90.dll. Verify the file exists and you can access it." The path obviously points to the location where the sources should have been cached, but the merge modules do not exist at that location. In addition, the compiler output in the IDE is identical to the command line output.

I can fix this by turning "Always cache setup sources" off, or by creating a "Compressed Web-Based EXE". This works for now, but I will need to change my deployment scenario in the future and would prefer not to have to use a Web-Based EXE.
It would be much appreciated if this is fixed in a future release.

We'll take a look at this. Thank you for the concise, detailed report!

Hello,
Can you tell me if any resolution was found for this?

Dear moldev,

I am afraid no resolution has been issue to this problem as of yet. Please keep using the workaround you described above.
We apologize for the inconvenience.