Hey Sergey,

Here's another "Can I do this..." question. The scenario:
- Our VFP7-based app has treated us well
- VFP8 version in the works. Quite desirable because of its improved image-handling capabilities.
- Customers have been installing the VFP7 version using an MSI, no problems
- More customers will be doing the same (a lot more).
- I want these new customers to be VFP8-capable without needing to install two MSI's, So.....
Can I create an MSI containing a VFP7 exe, but also have the MSI contain both the VFP7 _and_ the VFP8 run-time support files? One big advantage of this is that it requires an administrator to install an MSI for "All Users". Since the exe we deploy automatically keeps itself up to date via HTTP, we can conceivably auto-jump the deployed exe from V7 to V8 in a seamless fashion if we can get the V7 and V8 runtime files installed with the V7 build of our app, and then let it auto-update to V8 when we're comfortable with it.


>>Hi,
>>
>>I experienced the same thing you did. I had to start from scratch because I ended up chasing shadows (missing files) as you did. Now everything builds properly except for one thing. When I check the checkbox for Microsoft GDI+ I get a build error:
>>** fatal error: Error merging GDI Plus Redist module with module ID: c:\Program Files\Common Files\Merge Modules\VFP_GDIPlus.msm
>>
>>What is that?
>
>Hi Neil,
>
>Don't check Microsoft GDI+ merge module. VFP8 has it's own merge module VFP_GDIPlus.msm for GDI+. In ISX it's listed as 'GDI Plus Redist module'.