This has been brought up before, but It Would Be Nice :) if the .NET client
were CLS-compliant.
For example, the lack of this prevents the client from being used in
PowerShell (for, say, SCOM monitoring):
Add-Type -Path "RabbitMQ.Client.dll"
$connectionFactory = New-Object RabbitMQ.Client.ConnectionFactory
New-Object : The field/property: "Uri" for type:
"RabbitMQ.Client.ConnectionFactory" differs only in case from the
field/property: "uri". Failed to use non CLS compliant type.
All it takes to enforce this is adding
[assembly: CLSCompliant(true)]
to the AssemblyInfo.cs, then turning on Treat warnings as errors. Please
consider this. Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20111116/642215c4/attachment.htm>