Can anyone point me to or provide me a description of what makes or made up the 
DOTNET bindings?


I have the time, resources and client who has an interest in them.


Thanks,


Paul


________________________________
From: Flores, Paul A. <[email protected]>
Sent: Tuesday, May 1, 2018 3:43 PM
To: [email protected]
Subject: Re: DOTNET Binding Availablity

Thanks!


________________________________
From: Chuck Rolke <[email protected]>
Sent: Tuesday, May 1, 2018 3:40 PM
To: [email protected]
Subject: Re: DOTNET Binding Availablity

No. The qpid-cpp binding for dotnet has fallen into disuse and has
not been maintained for a couple of years.

For .NET I have been using https://github.com/Azure/amqpnetlite
which is a lightweight, native library. It does not have the same API
as qpid-cpp messaging but it is closely coupled with AMQP 1.0.
If you know AMQP then using AMQP.Net Lite should be fairly intuitive.

AMQP.Net Lite does not support older versions of AMQP 0.x.


----- Original Message -----
> From: "Paul A. Flores" <[email protected]>
> To: [email protected]
> Sent: Tuesday, May 1, 2018 5:09:30 PM
> Subject: DOTNET Binding Availablity
>
> Hi All,
>
>
> Is there DOTNET binding support available for Visual Studio 15 2017 for
> qpid-cpp-1.38.0?
>
>
> Thanks!
>
>
> Paul
>
>
> ________________________________
>
> This communication (including any attachments) may contain information that
> is proprietary, confidential or exempt from disclosure. If you are not the
> intended recipient, please note that further dissemination, distribution,
> use or copying of this communication is strictly prohibited. Anyone who
> received this message in error should notify the sender immediately by
> telephone or by return email and delete it from his or her computer.
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



________________________________

This communication (including any attachments) may contain information that is 
proprietary, confidential or exempt from disclosure. If you are not the 
intended recipient, please note that further dissemination, distribution, use 
or copying of this communication is strictly prohibited. Anyone who received 
this message in error should notify the sender immediately by telephone or by 
return email and delete it from his or her computer.


________________________________

This communication (including any attachments) may contain information that is 
proprietary, confidential or exempt from disclosure. If you are not the 
intended recipient, please note that further dissemination, distribution, use 
or copying of this communication is strictly prohibited. Anyone who received 
this message in error should notify the sender immediately by telephone or by 
return email and delete it from his or her computer.

Reply via email to