Home Forums WPF controls Xceed DataGrid for WPF XAML DataBinding Broken in VS 2008 Beta 2

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • User (Old forums)
    Member
    Post count: 23064
    #23975 |

    I have a project using the DataGrid for WPF that was developed in VS 2005 with the WPF Extensions. This project uses DataBinding in the XAML and works great. However, we recently made the move to VS 2008 Beta 2 due to bug fixes and general design time enhancements. With this move our XAML DataBinding is now broken. The only way we can do the binding now is to use c# code to perform the binding. Is anyone else experiencing this problem? Could there be a bug in the Xceed Grid?

    Imported from legacy forums. Posted by Patrick (had 727 views)

    User (Old forums)
    Member
    Post count: 23064

    For what it’s work I have a SIMPLE test project using ONE-WAY bindings against embedded XML data inside my Window XAML file.

    After the move to VS2008 Beta 2 the bindings continue to work.

    My test box is running Vista and VS2008 and the latest Xceed grid version.

    My install went smoothly after sorting out a problem with a bad DVD burn.

    Followed the readme at http://go.microsoft.com/fwlink/?LinkID=93822

    I also ran script mentioned at the end of this blog entry for fixing the ASP.NET Ajax issue:
    http://weblogs.asp.net/scottgu/archive/2007/07/26/vs-2008-and-net-3-5-beta-2-released.aspx

    Imported from legacy forums. Posted by Richard (had 316 views)

    User (Old forums)
    Member
    Post count: 23064

    ** Note:

    On my install I had to remove “Microsoft Visual Studio Web Authoring Component” even though the README calls it ” 10.Remove “Visual Web Developer Design Service Reminder Tools”.

    Rick Strahl made me aware of this in this post http://www.west-wind.com/weblog/posts/123925.aspx

    Imported from legacy forums. Posted by Richard (had 264 views)

    User (Old forums)
    Member
    Post count: 23064

    It looks like the XAML defined DataGridCollectionViewSource data stores now require a Path=View in the binding.

    Testing some of the test examples in VS2008 I found this to be the case.

    For example the “CustomViews” sample defines cvsEmployees as follows:

    <code>

    <xcdg:DataGridCollectionViewSource x:Key=”cvsEmployees”
    Source=”{Binding Source={x:Static Application.Current},Path=Employees}”>
    <xcdg:DataGridCollectionViewSource.SortDescriptions>
    <compModel:SortDescription PropertyName=”LastName”/>
    </xcdg:DataGridCollectionViewSource.SortDescriptions>
    </xcdg:DataGridCollectionViewSource>
    </code>

    But to consume this as an ItemsSource, I must use Path=View. This wasn’t needed in Orcas Beta1. Something seems to have changed on this.

    <code>
    <xcdg:DataGridControl x:Name=”grid”
    ItemsSource=”{Binding Source={StaticResource cvsEmployees}, Path=View}”
    CellEditorDisplayConditions=”None”
    EditTriggers=”None”
    ReadOnly=”True”
    ItemScrollingBehavior=”Immediate”
    NavigationBehavior=”RowOnly”>
    </code>

    Imported from legacy forums. Posted by Richard (had 285 views)

    User (Old forums)
    Member
    Post count: 23064

    I can also get simple XML Data Binding to work through XAML also. However what does not work is binding to a DataTable. If the binding happens in code it works. It is just when the binding is done through XAML that it doesn’t work.

    Imported from legacy forums. Posted by Patrick (had 551 views)

    User (Old forums)
    Member
    Post count: 23064

    Sorry, I did not read your response before posting my reply. Path=View does work.

    Thanks!

    Imported from legacy forums. Posted by Patrick (had 4677 views)

Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.