Hi Emile,<div><br>I found the problem with .Net client 2.4.1, and also I just pulled from the repository this afternoon revision 643 on default branch. It appears to have bug23887 merged into default.</div><div><br></div><div>
-Dan<br><br><div class="gmail_quote">On Mon, May 23, 2011 at 4:55 PM, Emile Joubert <span dir="ltr"><<a href="mailto:emile@rabbitmq.com">emile@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi Dan,<br>
<br>
On 23/05/11 16:25, Dan B wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all,<br>
<br>
I've been playing around with the .Net client solution with a view to<br>
using RabbitMQ with WCF.<br>
I have changed my RabbitMQ username and password, so the WCF examples<br>
explode because the ConnectionFactories are being initialized with the<br>
default values.<br>
</blockquote>
<br>
A bug with a similar description was fixed and released in version 2.4.0 - can you please confirm which release of the .net client library you are using? If you are building from source, does it include the merge of branch bug23887?<br>
<br>
If you still experience problems with the WCF binding included in the latest release of the .net client library then please follow-up with details.<br>
<br>
<br>
Thanks<br><font color="#888888">
<br>
Emile<br>
</font></blockquote></div><br></div>