>Hi Thomas,
>Thanks for the thread which is bring a lot of useful information of this rarely mentioned technique ie building a single manifest with possibly one or even a host of ocx-es and or COM registrable Dlls. And bringing all this stuff into the VFP executable when "building exe".
>
>I have read, as possibly most here, the posts by Rick Strahl and a few other pointers. But That remains untested and a bit difficult to grasp. I read that Dlls may or not work properly. I'd be glad if a UT-er with a large experience of the matter could share their experience. Especially with numerous non-MS components.
>
>Thanks again for the post - Daniel


Here is an example of what we use (shortened as there are 16 OCXs involved)

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
  <assemblyIdentity version="1.0.0.0" type="win32" name="Microsoft.VisualFoxPro" processorArchitecture="x86" />
  <description>Umana HR and pay</description>
  <dependency>
    <dependentAssembly>
      <assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" language="*" processorArchitecture="x86" publicKeyToken="6595b64144ccf1df" />
    </dependentAssembly>
  </dependency>
  <file name="ctcalendar.ocx">
    <comClass description="ctCalendar Control" clsid="{AAED59A9-6D5F-11D5-A85E-0080C8DFC881}" progid="CTCALENDARLib.ctCalendar" threadingModel="Both" />
  </file>