Apply CategoryAttribute fix to XamlDirectiveTest.cs too

svn path=/trunk/mcs/; revision=160443

diff --git a/mcs/class/System.Xaml/Test/System.Xaml/ChangeLog b/mcs/class/System.Xaml/Test/System.Xaml/ChangeLog
index ae1350d2b67da568101bf4918a163ce9edc674b4..568a0c69dbeecd119f7b7243c4ab74ea18d0b817 100644 (file)
--- a/mcs/class/System.Xaml/Test/System.Xaml/ChangeLog
+++ b/mcs/class/System.Xaml/Test/System.Xaml/ChangeLog
@@ -4,6 +4,7 @@
        portable way to resolve the CategoryAttribute ambiguity.
        * XamlObjectReaderTest.cs, XamlObjectWriterTest.cs: Likewise.
        * XamlTypeTest.cs, XamlXmlReaderTest.cs, XamlXmlWriterTest.cs: Likewise.
+       * XamlDirectiveTest.cs: Likewise.
 
 2010-05-17  Atsushi Enomoto  <atsushi@ximian.com>
 

diff --git a/mcs/class/System.Xaml/Test/System.Xaml/XamlDirectiveTest.cs b/mcs/class/System.Xaml/Test/System.Xaml/XamlDirectiveTest.cs
index 30d584a1f9a0ea93e1d89b7839cdbadf5c66164d..e57f9c7c20db7f13e0e51171267c37504e3e6ed7 100755 (executable)
--- a/mcs/class/System.Xaml/Test/System.Xaml/XamlDirectiveTest.cs
+++ b/mcs/class/System.Xaml/Test/System.Xaml/XamlDirectiveTest.cs
@@ -29,7 +29,7 @@ using System.Xaml;
 using System.Xaml.Schema;
 using NUnit.Framework;
 
-using Category = NUnit.Framework.CategoryAttribute;
+using CategoryAttribute = NUnit.Framework.CategoryAttribute;
 
 namespace MonoTests.System.Xaml
 {