Bug 681047

Summary: A non-default namespace must be an explicit import
Product: [Mono] Mono: Class Libraries Reporter: Steven Schermerhorn <stevens+novell>
Component: Sys.XMLAssignee: Atsushi Enomoto <atsushieno>
Status: RESOLVED FIXED QA Contact: Mono Bugs <mono-bugs>
Severity: Normal    
Priority: P5 - None    
Version: SVN   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Bug Depends on: 681045    
Bug Blocks:    
Attachments: Example of issue

Description Steven Schermerhorn 2011-03-19 07:47:05 UTC
Created attachment 420333 [details]
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 the attached example, the value for one of the types comes from a second assembly that also makes use of the XmlnsDefinitionAttribute. However, when the namespace is imported an unsupportedexcetion is thrown.

The example works if the clr-namespace is explicitly set.

Reproducible: Always

Steps to Reproduce:
1) run the repo
2) try the commented out way in the CurrentVersion.xaml file. (Remember that a comment can't be between the angle brackets, at least that is the case in .net)
Actual Results:  
using the url doesn't work

Expected Results:  
Namespaces should be able to be referred to by their urls
Comment 1 Atsushi Enomoto 2011-03-22 06:10:26 UTC
(continued from bug #681046) I noticed "TypeOtherAssembly" in the XmlnsDefinitionAttribute should be updated too. And after reflecting the change, now mono seems working fine. (They were due to the same reason I think, assembly resolution didn't happen and hence storing namespaces didn't occur as well.)