已答复 DataView binding bug: still alive?

全部回复

  • 2010年3月2日 7:35
    版主
     
     

    Hi Sinix,

    The issue is fixed in .net 4.0. See more information in the follow link:
    https://connect.microsoft.com/VisualStudio/feedback/details/389689/dataview-binding-related-issues-no-propertychanged-events

    Improving the quality of the products and services is a never-ending process for Microsoft. Thanks again for choosing us.

    Best regards,
    Linda Liu


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
  • 2010年3月2日 11:58
     
     
    Linda Liu, did you mention who feedbacked the issue?;)

    Ron Barone says,
    <CollectionViewSource x:Key="cvsParentT" />
      <CollectionViewSource x:Key="cvsChildT" Source="{Binding Source={StaticResource cvsParentT}, Path=FK_ParentT_ChildT}" />

    stops working if parent key updated.

    I'm still not sure the case posted by Ron Barone is the same as I feedbacked.
    Unfortunately, I'm deeply burried in non-wpf app for now and have not enough time to validate the trouble. Ill try to repro it at home and post results here.


  • 2010年3月2日 16:44
     
     已答复
    Linda Liu, unfortunately this is a bug. Feedbacked at https://connect.microsoft.com/VisualStudio/feedback/details/538103/wpf-dataset-master-detail-binding-issue.

    Sample at http://sites.google.com/site/whocodes/home/WpfBinding.zip (Instructions are listed on the sample's screen).
  • 2010年3月4日 1:24
     
     
    Dear Linda, please, reopen the bug I've feedbacked at https://connect.microsoft.com/VisualStudio/feedback/details/538103/wpf-dataset-master-detail-binding-issue.

    WPF binding (or RelatedDataView class itself) does not nandle case when master's key changed. Detail's keys ARE changed (FK's update rule set to cascade), but they are not displayed.

    I really dislike the quiality of conect service. Every time I feedbacked, I need to run 2-3 loops of cross-comments on multiple threads on forums before getting any reaction (not positive, as a rule). It's take eight month just to connect with DataSet team member and finally report the previus bug directly to him. This time will be the same?
  • 2010年3月5日 3:27
    版主
     
     已答复

    Hi Sinix,

    Microsoft has replied your feedback, and it seems an ADO bug, I think ADO team will process it as soon as possible.
    Thank you very much for your effects to improving the quality of the product from Microsoft.

    Best regards,
    Linda Liu


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
    • 已标记为答案 Sinix 2010年3月16日 7:35
    •  
  • 2010年3月5日 4:08
     
     
    Thanks for quick reaction!
  • 2012年4月16日 8:58
     
     

    Still am facing aame issue , Is ther any solution?


  • 2012年5月25日 2:55
     
     建议的答复

    Hi Linda,

    Still am facing same issue. i am using 4.0 framework only.please update the about this bug

  • 2012年5月31日 8:50
     
     
    it seems this bug  is  fixed in 4.0

    siva

  • 2012年7月2日 20:17
     
     

    I'm experiencing the same issue (with .Net 4.0).  This bug has NOT been fixed yet.

    What's the best workaround for now.  Thanks.