[rabbitmq-users] AMQP .Net Client to run on .Net Framework 2.0

[Vinoth Kumar]

Hi,



We are planning to use AMQP .Net client in one of our application to
consume messages from Rabbit MQ server. The system in which we deploy the
message consumer application is having only .Net Framework 2.0 and can’t be
upgraded to Framework 3.5. As per my understanding the minimum .net
framework required for the latest AMQP .Net client is 3.5.



Now we left with only one option that is to downgrade the AMQP .Net client
to target to .Net Framework 2.0. . Is this the right approach? or can I
download any of the earlier version of AMQP .Net client which will work in
.Net Framework 2.0?.

Can you please let me know what will be the impact on the functionalities
and the performance if we downgrade the AMQP .Net client to target to .Net
framework 2.0?



Note : We are not using the WCF binding functionalities in our application.


Thanks in advance.


Regards,
Vinoth

[Michael Klishin]

.NET client 3.3 or 3.2 should work on .NET 2 and can be used with any RabbitMQ version starting with 2.0. So simply use an earlier client, the API barely changed between recent releases.

Note that future client releases will require .NET 4.0.

MK

Hi,
We are planning to use AMQP .Net client in one of our application to consume messages from Rabbit MQ server. The system in which we deploy the message consumer application is having only .Net Framework 2.0 and can’t be upgraded to Framework 3.5. As per my understanding the minimum .net framework required for the latest AMQP .Net client is 3.5.
Now we left with only one option that is to downgrade the AMQP .Net client to target to .Net Framework 2.0. . Is this the right approach? or can I download any of the earlier version of AMQP .Net client which will work in .Net Framework 2.0?.
Can you please let me know what will be the impact on the functionalities and the performance if we downgrade the AMQP .Net client to target to .Net framework 2.0?
Note : We are not using the WCF binding functionalities in our application.
Thanks in advance.
Regards,
Vinoth
--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
For more options, visit https://groups.google.com/d/optout.

[Vinoth Kumar]

Thanks *Michael Klishin f*or the quick response.

Regards,

Vinoth

Post by Michael Klishin
.NET client 3.3 or 3.2 should work on .NET 2 and can be used with any
RabbitMQ version starting with 2.0. So simply use an earlier client, the
API barely changed between recent releases.
Note that future client releases will require .NET 4.0.
MK
Hi,
We are planning to use AMQP .Net client in one of our application to
consume messages from Rabbit MQ server. The system in which we deploy the
message consumer application is having only .Net Framework 2.0 and can’t be
upgraded to Framework 3.5. As per my understanding the minimum .net
framework required for the latest AMQP .Net client is 3.5.
Now we left with only one option that is to downgrade the AMQP .Net client
to target to .Net Framework 2.0. . Is this the right approach? or can I
download any of the earlier version of AMQP .Net client which will work in
.Net Framework 2.0?.
Can you please let me know what will be the impact on the functionalities
and the performance if we downgrade the AMQP .Net client to target to .Net
framework 2.0?
Note : We are not using the WCF binding functionalities in our application.
Thanks in advance.
Regards,
Vinoth
--
You received this message because you are subscribed to the Google Groups
"rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
<javascript:>.
For more options, visit https://groups.google.com/d/optout.