Setting the namespace to something different from null would be enough to avoid the WPF bug. It should also prevent the same kind of bugs in code making the assumption that namespace is *always* a non null string. It was indeed surprising for me (even if perfectly valid) to see a class with null namespace.
Thank you very much for the quick reply. Marco --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
