Are you running windows 64 bit? Did you build any of the C++ or WCF components as 32bit assemblies? The error you are seeing often results from mixing assembly types.
If you built your final exe as "Any CPU", it will start out as 64 bit by default and fail when loading any of the 32 bit components. You can force it to start as 32 bit by: CorFlags.exe foo.exe /32Bit+ Cliff On Wed, Jun 20, 2012 at 1:06 AM, Ramith Jayasinghe <[email protected]> wrote: > Hi > I was able to build the WCF/C++ successfully ( - even if I had to manually > to add ""$(BOOST_ROOT)\stage\lib" to 'Additional Library Directories"). > I didn't try to run tests. But I want to try out the samples provided. The > most simplest sample [1] and WCFToWCFDirect also fails with following > errors. In Jira I found a similar issue [1]. However, the way Steve managed > to resolve the issue is bit tricky for me to understand. > It would be great if Steve could shed some light on this? > > > ----------Error------------------ > Could not load file or assembly 'Apache.Qpid.Interop, > Version=1.0.4554.22600, Culture=neutral, PublicKeyToken=679e1f50b62dbace' > or one of its dependencies. An attempt was made to load a program with an > incorrect format. > --------------------------- > > [1] > http://svn.apache.org/repos/asf/qpid/trunk/qpid/wcf/samples/Channel/HelloWorld/ > [2] > http://svn.apache.org/repos/asf/qpid/trunk/qpid/wcf/samples/Channel/WCFToWCFDirect/ > [3] https://issues.apache.org/jira/browse/QPID-2135 > > Regards, > Ramith Jayasinghe > > On Mon, Jun 18, 2012 at 8:55 PM, Steve Huston <[email protected]> wrote: > >> Ok, Ramith - you should have no problem with that approach. >> >> -Steve >> -- >> Steve Huston, Riverace Corporation >> Total Lifecycle Support for Your Networked Applications >> http://www.riverace.com >> >> > -----Original Message----- >> > From: Ramith Jayasinghe [mailto:[email protected]] >> > Sent: Friday, June 15, 2012 12:29 PM >> > To: [email protected] >> > Subject: Re: Building Qpid/WCF Bindings in Visual Studio 2010 (64Bit) on >> > Windows 7 >> > >> > Hi Steve, >> > Thanks for the reply. >> > I think I'm going to try out this with vs2008. >> > Regards >> > Ramith Jayasinghe >> > >> > On 14 Jun, 2012, at 9:27 PM, "Steve Huston" <[email protected]> >> wrote: >> > >> > > Hi Ramith, >> > > >> > > I actually tried this out when building the 0.16 kits... what you >> > > noted is correct. >> > > >> > >> This is similar to my previous query about building qpid with vs2010. >> > >> However this time I want to build Qpid/WCF bindings using vs2010 >> > > (64-bit). >> > >> It seems solution/project files are all in visual studio 2008 and >> > > converting >> > >> them automatically 2010 results in quite a bit of warnings (in >> > >> Interop >> > > Project), >> > >> when it was built results in a failure (with lots of errors). >> > >> So my questions are: >> > >> is there a plan to port the project to vs2010? >> > > >> > > Not a formal one, no. I plan to get around to it if no one else does >> it. >> > > If someone funds the work, I'd get to it a lot faster. >> > > >> > >> is there something I'm doing wrong (when building the project)? >> > > >> > > No. I had the same problems. >> > > >> > >> has anyone tried wcf/bindings with .NET framework v 4? >> > > >> > > Not that I'm aware of, no. >> > > >> > > -Steve >> > > >> > > -- >> > > Steve Huston, Riverace Corporation >> > > Total Lifecycle Support for Your Networked Applications >> > > http://www.riverace.com >> > > >> > > >> > > --------------------------------------------------------------------- >> > > To unsubscribe, e-mail: [email protected] For >> > > additional commands, e-mail: [email protected] >> > > >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [email protected] For additional >> > commands, e-mail: [email protected] >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
