Missed in a previous commit. Updated README from Chuck Rolke.

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@982261 13f79535-47bb-0310-9956-ffa450edef68

1 files changed, 65 insertions, 10 deletions

diff --git a/cpp/README-winsdk.txt b/cpp/README-winsdk.txt
index 8582852153..76d5f56681 100644
--- a/cpp/README-winsdk.txt
+++ b/cpp/README-winsdk.txt
@@ -1,12 +1,13 @@
-			Qpid-Cpp-Win-Sdk
-			================
+            Qpid-Cpp-Win-Sdk
+            ================
 
 Table of Contents
 =================
 1. Introduction
 2. Prerequisites
 3. Kit contents
-4. Notes
+4. Building dotnet_examples
+5. Notes
 
 
 1. Introduction
@@ -42,28 +43,82 @@ The kit directories hold the content described here.
       the associated debug program database (.pdb) files.
     Boost library files.
     MSVC90 runtime library files.
-	
+
   \include
     A directory tree of .h files.
-	
+
   \lib
     The linker .lib files that correspond to files in /bin.
-	
+
   \docs
     Apache Qpid C++ API Reference
-	
+
   \examples
     A Visual Studio solution file and associated project files 
     to demonstrate using this SDK in C++.
-		
+
+  \dotnet_examples
+    A set of example source files written in C#, Visual Basic, and
+    PowerShell.
+
   \management
     A python scripting code set for generating QMF data structures.
     
     For more information on Qpid QMF go to:
     https://cwiki.apache.org/qpid/qpid-management-framework.html
 
-	
-4. Notes
+
+4. Building dotnet_examples
+===========================
+
+Each file in the \dotnet_examples directory is a stand-alone, main
+console program that illustrates some facet of programming the Qpid 
+Messaging API. Use the following steps to create a project that
+builds and executes an example csharp program.
+
+A. Assume that the WinSdk was downloaded to d:\winsdk.
+B. Start Visual Studio
+C. Add File->New->Project...
+   1. Select C#, Console Application
+   2. Name: csharp.direct.receiver
+   3. Location: D:\winsdk\dotnet_examples
+   4. Check: "Create directory for solution"
+   5. Press OK
+D. In Solution Explorer
+   1. Delete program.cs
+   2. Add->Existing Item. 
+      Select d:\winsdk\dotnet_examples\csharp.direct.receiver.cs
+   3. Add Reference to d:\winsdk\bin\org.apache.qpid.messaging.dll
+      Note: In each source file a 'using' statement selects
+      Org.Apache.Qpid.Messaging, Org.Apache.Qpid.Messaging.Sessionreceiver,
+      or both. Resolve these statements with references to the files
+      in \bin.
+   4. Right-click the project and select Properties
+      Select the Build tab.
+      Select Configuration pulldown entry "All Configurations"
+      Set the Output Path to "d:\winsdk\bin"
+E. Right-click the solution and select Configuration Manager
+   1. Select Configuration -> Debug
+   2. Select Platform -> <new>
+      pick x86, OK
+F. In the standard toolbar verify that
+   1. Configuration selects Debug
+   2. Platform selects x86
+G. Build the solution.
+   1. The solution should build with no errors or warnings.
+H. Verify that the solution placed the executables in the proper place:
+   1. Directory d:\winsdk\bin has files csharp.direct.receiver.exe,  
+      csharp.direct.receiver.pdb, and csharp.direct.receiver.vshost.exe.
+
+The solution is now ready to execute. You may set breakpoints in the
+Visual Studio source file or run the executable directly from 
+d:\winsdk\bin.
+
+This process may be repeated for each example csharp source file. A similar
+process is followed for the Visual Basic example. The PowerShell example
+is executed directly in a PowerShell window.
+
+5. Notes
 ========
 * The Qpid-Cpp binaries are produced for the 32-bit Win32 platform.