https://bugzilla.novell.com/show_bug.cgi?id=681045
https://bugzilla.novell.com/show_bug.cgi?id=681045#c0 Summary: Only one assembly can make use of the same xmlns namespace Classification: Mono Product: Mono: Class Libraries Version: SVN Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Sys.XML AssignedTo: [email protected] ReportedBy: [email protected] QAContact: [email protected] Found By: --- Blocker: --- Created an attachment (id=420331) --> (http://bugzilla.novell.com/attachment.cgi?id=420331) Example of issue User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_6; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16 In .NET multiple assemblies can have the XmlnsDefinitionAttribute assembly attribute defined for the same namespace. The idea being that you can use the same url in all of your XAML files and it'll magically find the right type across all of the assemblies. It looks like Mono's implementation only allows one assembly to use a namespace. Attached is a repro. Reproducible: Always Steps to Reproduce: 1. Create two assemblies that specify the same XAML namespace, but map them to different .NET namespaces. 2. Try to load xaml with the specified XAML namespace as the default namespace in the file. Actual Results: Duplicate key exception Expected Results: All .net namespaces and types in marked assemblies to be mapped to the XAML namespace. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
