<div dir="ltr"><p>We are using .NET 2.0 and should be moving up to 3.5 in the next couple of month.</p><p>I support dropping 1.1 and rewrting the code to use the benefits of 2.0 (.NET 3.5 actually runs .NET CLR 2.0 SP1, so its almost the same as .NET 2.0 in terms of compiler capabilities and runtime capablities, the only difference is in some of the added libraries), i.e. Generics and friends (thought the rewrite can wait for a later release).<br>
</p><p>:-)</p><p>Eran</p><p></p><br><div class="gmail_quote">On Thu, Feb 19, 2009 at 12:44 PM, Emile Joubert <span dir="ltr"><<a href="mailto:emile@lshift.net">emile@lshift.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Hi all,<br>
<br>
We are contemplating dropping backwards compatiblity with .NET 1.1 when<br>
building the RabbitMQ .NET/C# client from source. It will be useful to<br>
get an indication of how many people will be negatively affected by this<br>
decision.<br>
<br>
Details about .NET support are here: <a href="http://www.rabbitmq.com/dotnet.html" target="_blank">http://www.rabbitmq.com/dotnet.html</a><br>
The binary packages for release 1.5.1 are already compiled for .NET 2.0<br>
or later. The motivation for dropping source compatibility with .NET 1.1<br>
is to remove the dependency on deprecated classes.<br>
<br>
<br>
Thanks for any feedback<br>
<br>
<br>
-Emile<br>
<br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</blockquote></div><br></div>