Aha!!!! The runtime environment is finding my installation of qpid 0.22!!!! It ought to be looking at the .dlls for the latest version of Qpid. I'm going to pursue this.
Thanks to this list for serving as a place for soliloquy, A On Thu, Jul 23, 2015 at 11:24 AM, Andrew Hartline <[email protected]> wrote: > I have managed to build qpid-cpp for Windows, got all the examples to > compile, and got some of my own code to compile with dependencies on Qpid. > I am now getting some runtime errors. DependencyWalker says: > > Error: The Side-by-Side configuration information for "c:\program files > (x86)\apache\qpidc-0.22\bin\QPIDMESSAGINGD.DLL" contains errors. The > application has failed to start because its side-by-side configuration is > incorrect. Please see the application event log or use the command-line > sxstrace.exe tool for more detail (14001). > Error: The Side-by-Side configuration information for "c:\program files > (x86)\apache\qpidc-0.22\bin\QPIDCLIENTD.DLL" contains errors. The > application has failed to start because its side-by-side configuration is > incorrect. Please see the application event log or use the command-line > sxstrace.exe tool for more detail (14001). > Error: The Side-by-Side configuration information for "c:\program files > (x86)\apache\qpidc-0.22\bin\QPIDCOMMOND.DLL" contains errors. The > application has failed to start because its side-by-side configuration is > incorrect. Please see the application event log or use the command-line > sxstrace.exe tool for more detail (14001). > Error: The Side-by-Side configuration information for "c:\program files > (x86)\apache\qpidc-0.22\bin\QPIDTYPESD.DLL" contains errors. The > application has failed to start because its side-by-side configuration is > incorrect. Please see the application event log or use the command-line > sxstrace.exe tool for more detail (14001). > > > Sxstrace.exe says: > > INFO: Parsing Manifest File C:\Program Files > (x86)\Apache\qpidc-0.22\bin\qpidmessagingd.dll. > INFO: Manifest Definition Identity is (null). > INFO: Reference: > Microsoft.VC90.DebugCRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8" > INFO: Resolving reference > Microsoft.VC90.DebugCRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8". > INFO: Resolving reference for ProcessorArchitecture WOW64. > INFO: Resolving reference for culture Neutral. > INFO: Applying Binding Policy. > INFO: No publisher policy found. > INFO: No binding policy redirect found. > INFO: Begin assembly probing. > INFO: Did not find the assembly in WinSxS. > INFO: Attempt to probe manifest at > C:\WINDOWS\assembly\GAC_32\Microsoft.VC90.DebugCRT\9.0.21022.8__1fc8b3b9a1e18e3b\Microsoft.VC90.DebugCRT.DLL. > INFO: Did not find manifest for culture Neutral. > INFO: End assembly probing. > INFO: Resolving reference for ProcessorArchitecture x86. > INFO: Resolving reference for culture Neutral. > INFO: Applying Binding Policy. > INFO: No publisher policy found. > INFO: No binding policy redirect found. > INFO: Begin assembly probing. > INFO: Did not find the assembly in WinSxS. > INFO: Attempt to probe manifest at > C:\WINDOWS\assembly\GAC_32\Microsoft.VC90.DebugCRT\9.0.21022.8__1fc8b3b9a1e18e3b\Microsoft.VC90.DebugCRT.DLL. > INFO: Attempt to probe manifest at C:\Program Files > (x86)\Apache\qpidc-0.22\bin\Microsoft.VC90.DebugCRT.DLL. > INFO: Attempt to probe manifest at C:\Program Files > (x86)\Apache\qpidc-0.22\bin\Microsoft.VC90.DebugCRT.MANIFEST. > INFO: Attempt to probe manifest at C:\Program Files > (x86)\Apache\qpidc-0.22\bin\Microsoft.VC90.DebugCRT\Microsoft.VC90.DebugCRT.DLL. > INFO: Attempt to probe manifest at C:\Program Files > (x86)\Apache\qpidc-0.22\bin\Microsoft.VC90.DebugCRT\Microsoft.VC90.DebugCRT.MANIFEST. > INFO: Did not find manifest for culture Neutral. > INFO: End assembly probing. > ERROR: Cannot resolve reference > Microsoft.VC90.DebugCRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8". > > > I hope that this is a fairly simple issue. Can anyone point me towards a > solution? > > Thanks! > > Andrew Hartline >
