Grid top level namespace

Thread is closed for posting
3 posts, 1 answers
  1. Bernhard König
    Bernhard König avatar
    78 posts
    Member since:
    Nov 2009

    Posted 23 Nov 2014 Link to this post


    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.

  2. Answer
    Ves avatar
    2914 posts

    Posted 26 Nov 2014 Link to this post

    Hi Bernhard,

    Thanks for writing. We will fix it in the next release. Meanwhile, you can open a formal support ticket to get a build with a fix.

    Please, accept our apologies for the inconvenience.

    Best regards,

    Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.

  3. Bernhard König
    Bernhard König avatar
    78 posts
    Member since:
    Nov 2009

    Posted 26 Nov 2014 in reply to Ves Link to this post

    Hi Ves,

    thanks, good to know this will be changed!

Back to Top