Thanks, I figured it out. By the way, tar archives contain corrupted .sln files.
However, when I downloaded from svn everything worked fine, I am able to launch 
and debug now.

I already found and fixed a bug with indefinite wait loop in 
org.apache.qpid.client.Client.close() method.

-----Original Message-----
From: Gordon Sim [mailto:[email protected]] 
Sent: Friday, November 20, 2009 12:01 PM
To: [email protected]
Subject: Re: dotnet client sources vs. compiled dll

There are two different dotnet client libs on the download page, one for 
AMQP 0-10 [1] (in the org.apache.qpid.client), one for AMQP 0-8 and 0-9 
[2] (in the Apache.Qpid.Client namespace).

There appears to be no individual source tar ball for these, so I guess 
you have to get the sources from the full project tarball [3]. Within 
that the AMQP 0-10 client library is under dotnet/client-010/. I'm 
afraid I don't myself have any experience of building either of these, 
but perhaps someone else on the list may be able to help.

(I should perhaps note also that in the upcoming 0.6 release there will 
be a new WCF component that is built on top of the c++ client.)

[1] http://www.apache.org/dist/qpid/0.5/qpid-dotnet-0-10-0.5.zip
[2] http://www.apache.org/dist/qpid/0.5/qpid-dotnet-0-8-0.5.zip
[3] http://www.apache.org/dist/qpid/0.5/qpid-0.5.tar.gz
>
> So where do I get Dotnet client sources, preferably compilable and working?
>
> Thanks.
>
> --Alexei
>     yahoo: alexei.sosin
>     mts: 6021715
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:[email protected]
>


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[email protected]


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[email protected]

Reply via email to