qpid-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cctriel...@apache.org
Subject svn commit: r722739 - in /incubator/qpid/trunk/qpid/dotnet: README.txt RELEASE_NOTES.txt
Date Wed, 03 Dec 2008 03:27:26 GMT
Author: cctrieloff
Date: Tue Dec  2 19:27:26 2008
New Revision: 722739

URL: http://svn.apache.org/viewvc?rev=722739&view=rev
updated readme, release-notes from Aidan


Modified: incubator/qpid/trunk/qpid/dotnet/README.txt
URL: http://svn.apache.org/viewvc/incubator/qpid/trunk/qpid/dotnet/README.txt?rev=722739&r1=722738&r2=722739&view=diff
--- incubator/qpid/trunk/qpid/dotnet/README.txt (original)
+++ incubator/qpid/trunk/qpid/dotnet/README.txt Tue Dec  2 19:27:26 2008
@@ -1,20 +1,85 @@
-There is .NET client support for AMQP 0-8 and AMQP 0-10.
+There are two seperate .Net clients.
+One implements the AMQP 0-10 protocol and is located in the client-010
+directory, this can communicate with the C++ broker.
+Instructions for building and installing the 0-10 client are located in client-010/README.txt.
-AMQP 0-10
-A slef contained client that supports  WCF and xcel 
-is located the client-010
-Please see client-010/README.txt
+The other, located in the root of the dotnet directory implements the
+0-8 protocol, which can communicate with the Java broker.
+Instructions for building and installing the 0-9 client are below.
-AMQP 0-8 
-0-8 Client is located in this directory
-Please see README0-8.txt
+NOTE: The rest of this file is 0-8 specific 
+      For 0-10 go to client-010/README.txt
+  Microsoft Visual Studio 2005 (VS2005) or Mono 2.0
+  NAnt 0.85 - only required for builds outside VS2005 (.net 1.1, .net 2.0, mono 2.0)
+  Ant 1.6.5
+  Cygwin (or alternatively build via cmd but alter instructions below accordingly)
+Set up PATH to include Nant.exe:
+  $ PATH=/cygdrive/c/WINDOWS/Microsoft.NET/Framework/v2.0.50727:$PATH
+Set up PATH to include ant:
+Generate framing from Qpid.Common/amqp.xml specificiation file:
+  $ build-framing
+Alternatively, just switch to /Qpid.Common and run "ant" there.
+You can build from Visual Studio 2005 normally. Alternatively, you
+can build debug releases for any supported framework from the 
+command line using Nant:
+To build .NET 2.0 executables (to bin/net-2.0):
+  $ build-dotnet20
+To build .NET 1.1 executables (to bin/net-1.1):
+  $ build-dotnet11
+To build for Mono on Linux (to bin/mono-2.0):
+  $ build-mono
+For .NET 1.1
+  $ release net-1.1
+Generates ./bin/net-1.1/release/Qpid.NET-net-1.1-yyyyMMdd.zip
+For .NET 2.0
+  $ release net-2.0
+Generates ./bin/net-2.0/release/Qpid.NET-net-2.0-yyyyMMdd.zip
+For Mono
+  $ release mono-2.0
+Generates ./bin/mono-2.0/release/Qpid.NET-mono-2.0-yyyyMMdd.zip

Modified: incubator/qpid/trunk/qpid/dotnet/RELEASE_NOTES.txt
URL: http://svn.apache.org/viewvc/incubator/qpid/trunk/qpid/dotnet/RELEASE_NOTES.txt?rev=722739&r1=722738&r2=722739&view=diff
--- incubator/qpid/trunk/qpid/dotnet/RELEASE_NOTES.txt (original)
+++ incubator/qpid/trunk/qpid/dotnet/RELEASE_NOTES.txt Tue Dec  2 19:27:26 2008
@@ -1,22 +1,8 @@
+Apache Incubator Qpid .NET M4 Release Notes
-NOTE: The non 0-10 client located in client-010 
-This file contains release notes for 0-8 AMQP client completed
-for M2.
-Apache Qpid .NET 0-8 RELEASE NOTES
-The Qpid M2 release contains support the for AMQP 0-8 specification.
-You can access the 0-8 specification using the following link.
+The Qpid M4 release contains support the for AMQP 0-10 and AMQP 0-8
 For full details of Qpid capabilities, as they currently stand, see our
 detailed project documentation at:
@@ -34,48 +20,8 @@
-M2 Tasks Completed
-The set of JIRA tasks completed as part of the M2 effort is available at:
-Here is a filtered list of JIRA items for the .NET Client 
+Changes since M3
-Test           QPID-435     HeadersExchangeTest fails     
-New Feature    QPID-136     implement prefetch       
-New Feature    QPID-291     Support SASL authentication in .NET client       
-Improvement    QPID-246     Custom Exception types should be serializable       
-Improvement    QPID-312     Inconsistency in naming conventions       
-Improvement    QPID-338     Integrate JDK 1.4 compatible SASL API Library & CRAM-MD5
-Improvement    QPID-345     Implement Blocking receive modes in BasicMessageConsumer    
-Improvement    QPID-398     Implement SSL/TLS support in the .NET Client       
-Improvement    QPID-452     Improve Message Classes and Message Creation APIs       
-Improvement    QPID-489     Create new build system for .NET Client       
-Improvement    QPID-490     Improve AmqChannel.PurgeQueue() and AmqChannel.DeleteQueue()
-Improvement    QPID-495     Implement default timeouts for AttainState and SyncWriter operations
-Bug            QPID-546     .Net does not handle reply to fields correctly.
-Bug            QPID-237     Build broken because of missing IBytesMessage.Reset() impl in
-Bug            QPID-238     Wrong call to string.Split() in AbstractQmsMessage.GetExchangeName()
-Bug            QPID-239     Use of assembly name vs. assembly path in AMQConnection.LoadTransportFromAssembly()
-Bug            QPID-250     .Net client does not use specs from the specs directory.    
-Bug            QPID-257     Test HeadersMatchingConsumer#Test fails.       
-Bug            QPID-258     Test ServiceProvidingClient#Test fails.       
-Bug            QPID-259     Test ServiceRequestingClient#SendMessages fails.       
-Bug            QPID-267     AMQConnection#Stop throws NotImplementedException       
-Bug            QPID-284     .Net build broekn due to missing HeadersMatchingProducers   
-Bug            QPID-335     .NET Client messages not interoperable with Java client     
-Bug            QPID-384     Update AMQConstant.cs to match response codes in AMQP 0.9   
-Bug            QPID-385     Failover support sometimes masks authentication errors      

-Bug            QPID-441     .NET Client does not properly handle bounced (undeliverable)
-Bug            QPID-456     .NET Client doesn't enforce virtual host names start with '/'
-Bug            QPID-467     Complete Interop Testing       
-Bug            QPID-485     AmqBrokerInfo.Equals method doesn't get the expected result 
-Bug            QPID-486     .NET Client SASL implementation chooses first matching mechanism
instead of stronger       
-Bug            QPID-487     The QpidConnectionInfo.ToString() method returns a wrong value
-Bug            QPID-492     Race condition causes received messages to read wrong headers
and/or body       
+The major change since M3 has been the introduction of 0-10 support.

View raw message