Visual Studio 2003 C/C++ runtimes

[MortSkil]

In my Application Runtimes, MS Visual C++ Runtime 6.0 and 8.0 is both listed, but I miss 7.0/7.1. Did I miss something during installation, or is there no specific support for MS Visual Studio 2003 runtimes/merge modules?

[MichaelNesmith]

7.0/7.1 are not provided built-in, but you can easily run them from your setup using the Run Program command.

[MortSkil]

With VS 2003 and WfWI, I have been used to include these runtimes through merge modules.
Is it as easy as adding e.g. the VC_User_CRT71_RTL_X86_---.msm in Deployment::Merge Modules ?

How do you recommend treating the TARGETDIR property introduced/required by the MS merge module? In WfWI I had to execute a CA to assign INSTALLDIR to TARGETDIR in order to have the CRT installed in the INSTALLDIR directory instead of C:\\.

[MichaelNesmith]

Actually, if you use their stand-alone EXE installers, it will be easier than having to do the merge module stuff (their targeting).

Alternately with the MSMs, you may go ahead and directly write into the MSM database using Orca the target value of [TARGETDIR].

[MichaelNesmith]

Actually, if you use their stand-alone EXE installers, it will be easier than having to do the merge module stuff (their targeting).

Alternately with the MSMs, you may go ahead and directly write into the MSM database using Orca the target value of [TARGETDIR].

[MortSkil]

Where may I find the 7.0/7.1 redist executables? I have been using the MSM previously with Wise.

Why are 6.0 and 8.0 included as prerequisites/Application Runtimes but not 7.0?

I also found that the Scan operation in Files does not detect the 7.0/7.1 runtime dependencies. It would be nice if they did

[MichaelNesmith]

7.X was simply an oversight on our part - apologies for the inconvenience. You can easily add your own runtime installer for them - please just look at the scripts that the 8.0 installer uses, and copy/paste