Added some notes on how we can use and/or test this XamlReader under .NET.

diff --git a/mcs/class/System.Xaml/System.Xaml/XamlObjectReader-new.cs b/mcs/class/System.Xaml/System.Xaml/XamlObjectReader-new.cs
index e379d6409b7abe02a25e26352436ddcfff915bd7..4a1332702b81a400dfd42ce1746c410d5a42114f 100644 (file)
--- a/mcs/class/System.Xaml/System.Xaml/XamlObjectReader-new.cs
+++ b/mcs/class/System.Xaml/System.Xaml/XamlObjectReader-new.cs
@@ -20,8 +20,7 @@
 // OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
 // WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 //
-#define USE_NEW
-#if USE_NEW
+
 using System;
 using System.Collections;
 using System.Collections.Generic;
@@ -31,6 +30,22 @@ using System.Windows.Markup;
 using System.Xaml;
 using System.Xaml.Schema;
 
+//
+// This implementation can be compiled under .NET, using different namespace
+// (Mono.Xaml). To compile it into a usable library, use the following compile
+// optons and sources:
+//
+//     dmcs -d:DOTNET -t:library -r:System.Xaml.dll \
+//             System.Xaml/XamlObjectReader-new.cs \
+//             System.Xaml/XamlNode.cs \
+//             System.Xaml/TypeExtensionMethods.cs
+//
+// (At least it should compile as of the revision that this comment is added.)
+//
+// Adding Test/System.Xaml/TestedTypes.cs might also be useful to examine this
+// reader behavior under .NET and see where bugs are alive.
+//
+
 #if DOTNET
 namespace Mono.Xaml
 #else
@@ -156,5 +171,3 @@ namespace System.Xaml
                }
        }
 }
-
-#endif