> Thanks for the quick comeback Phil. Continuing to research the issues
> after my post, I came across a Microsoft document at
>
http://msdn.microsoft.com/en-us/vbrun/ms788708(printer).aspx that listed
> the vb runtime files that ship with Vista and should not be part of an
> install package. That list includes the 4 components that are in
> oleaut32.msm as well as msvbm60.dll and comcat.dll. But the paper says you
> should distribute with your application the ocx's like comct332.ocx,
> comdlg32.ocx, richtx32.ocx, etc. So I've removed the oleaut32.msm and the
> comcat.msm from the setup solution, but it appears that I need to leave in
> the others. Thus I suppose I should simply ignore those warning messages?
> Or should I forget about adding the msms and just go with the ocx's?
>
> "Phil Wilson" <phil.wilson[ at ]wonderware.something.com> wrote in message
> news:ef5xHixWJHA.5764[ at ]TK2MSFTNGP04.phx.gbl...
>> You don't need any of those merge modules (except the VB support in
>> msvbm60) for any OS since (and including) Windows 2000 when oleaut32 and
>> the rest became part of the OS instead of files that people installed.
>> That's why you won't find any updated merge modules containing those
>> files.
>>
>> --
>> Phil Wilson
>> Definitive Guide to Windows Installer
>>
http://www.apress.com/book/view/1590592972>>
>>
>> "Roy Soltoff" <rattlesnake0407[ at ]community.nospam> wrote in message
>> news:%23zfwe3tWJHA.1328[ at ]TK2MSFTNGP02.phx.gbl...
>>>I have a legacy VB6 project that has been supported only up through Win
>>>XP.
>>> As an aside, we have migrated the product years ago to VS2003, then to
>>> VS2005,
>>> and will port to VS2008 next year. The VB6 project group used the VB6
>>> PDW for
>>> deployment. We now have one client insisting on getting this to work on
>>> Vista.
>>> I've managed to revise the project group to compile and run on Vista
>>> using
>>> VB6-SP6. I'm in the process of building an installer (msi) for this
>>> project
>>> using a VS2008 Setup project.
>>>
>>> I have identified all the dependencies using the old setup.lst and are
>>> using
>>> all of the VB6-SP6 merge modules that Microsoft has made available. When
>>> I compile
>>> the setup project, I get repeated instances of the following two
>>> warnings:
>>> WARNING: Unable to find module dependency with signature
>>> 'OLEAUT32.8C0C59A0_7DC8_11D2_B95D_006097C4DE24'
>>> WARNING: Unable to find module dependency with signature
>>> 'COMCAT.3207D1B0_80E5_11D2_B95D_006097C4DE24'
>>> By looking at the ModuleDendencies list for the Microsoft msms (such as
>>> comdlg32.msm,
>>> coct232.msm, etc), I know that these are generating those depedencies.
>>> But I also have
>>> added the comcat.msm and the oleaut32.msm and the ModuleSignature for
>>> those are the
>>> signatures appearing in the warnings. I've been searching the net for a
>>> few days
>>> trying to reconcile this to no avail.
>>>
>>> I recognize that I will have to do something further ICW MS08-008
>>> described in
>>> article 946235 which reflects an OS-specific version of oleaut32.dll;
>>> but I would
>>> at least like to resolve these warnings before I proceed further.
>>>
>>> On another point, article 830761 last reviewed on May 18, 2007 (so its
>>> not that old)
>>> has this statement relating to Visual Studio Installer (an older
>>> version) and referring
>>> to the bootstrap files (comcat.dll, stdole2.tlb, asycfilt.dll,
>>> olepro32.dll,
>>> oleaut32.dll, and msvbm60.dll), "If you are using Visual Studio
>>> Installer to build an
>>> installer package, these files are already included in a merge module
>>> that is added
>>> to your installer package.". I have been unable to locate that; but I
>>> would gather that it
>>> has never been updated to VB6-SP6.
>>>
>>> It would be great to be able to find a prerequisite package that I could
>>> drop in to
>>> the prerequisites packages folder that would handle those bootstrap
>>> files similar to
>>> what Microsoft did with the MDAC 2.81 bootstrapper package.
>>>
>>
>>
>
>