This question is locked. New answers and comments are not allowed.
Hi,
there's a Grid namespace in Telerik.Controls.Xaml.Grid library. As this namespace is top-level, it interfers with classes of the same name, like the Windows.UI.Xaml.Controls.Grid when thte Windows.UI.Xaml.Controls namespace is imported by a using.
The same seems to be the case for other libraries, for example there is also an Input top level namespace.
While it can be worked around by using the fully qualified class name, it is not very nice. Is there a reason for this kind of naming? Couldn't be the classes in these top level namespaces also be moved into the Telerik.Controls.Xaml.Grid namespace instead of its own top-level Grid namespace?
Would be a lot nicer and prevent such collisions.
Thanks,
Bernhard
there's a Grid namespace in Telerik.Controls.Xaml.Grid library. As this namespace is top-level, it interfers with classes of the same name, like the Windows.UI.Xaml.Controls.Grid when thte Windows.UI.Xaml.Controls namespace is imported by a using.
The same seems to be the case for other libraries, for example there is also an Input top level namespace.
While it can be worked around by using the fully qualified class name, it is not very nice. Is there a reason for this kind of naming? Couldn't be the classes in these top level namespaces also be moved into the Telerik.Controls.Xaml.Grid namespace instead of its own top-level Grid namespace?
Would be a lot nicer and prevent such collisions.
Thanks,
Bernhard