xaml vs code-behind?

2 posts, 0 answers
  1. HowdyNeighbor
    HowdyNeighbor avatar
    1 posts
    Member since:
    Sep 2014

    Posted 09 Sep 2014 Link to this post

    Hello -
    We are about to start a new project that contains a grid with many, many columns. Although we have chosen Telerik for our grid control, we are trying to decide if it is best to create the columns in xaml, or in the code-behind. We have some questions that might help us decide between the xaml and code-behind options:

    1. Performance - Is there any performance drain/gain for either option? Especially with large amounts of data?
    2. Features - Ex...If a new column property is added in a new version, is it ever defaulted for one option, and not the other?
    3. Maintainability - Is one option better supported than the other, especially in terms of upgrades?

    Is there anything else we're not considering, or any issues that might sway us in one direction, versus another? Any information you can provide would be helpful.

  2. Dimitrina
    Dimitrina avatar
    3769 posts

    Posted 12 Sep 2014 Link to this post


    From the perspective of RadGridView, there is no difference between defining the columns in XAML or code behind. This applies to all your three questions, regarding Performance, Features and Maintainability.
    You can also check our online documentation on Defining Columns.

    Generally I would suggest you checking the Tips and Tricks suggestions on improving performance.

    Check out Telerik Analytics, the service which allows developers to discover app usage patterns, analyze user data, log exceptions, solve problems and profile application performance at run time. Watch the videos and start improving your app based on facts, not hunches.
Back to Top