Print Page | Close Window

Design issue of using data binding

Printed From: IdeaBlade
Category: DevForce
Forum Name: DevForce 2009
Forum Discription: For .NET 3.5
URL: http://www.ideablade.com/forum/forum_posts.asp?TID=1313
Printed Date: 28-Mar-2025 at 9:36am


Topic: Design issue of using data binding
Posted By: monkeyking
Subject: Design issue of using data binding
Date Posted: 08-Jun-2009 at 7:42pm
We are facing a design problem because of using databinding. as you known, any databinding control is only be able to connect with one data source. but in our situation, the required data source must combines severial different DB tables's info, so once we use Devforce object mapper to generate the Entities, we don't know which entity should be choosen to do data binding, because they are DB tables and none of them is suitable to be the data source. so should we create our own databinding source manually? or Devforce has a solution to deal with our problem.  


Replies:
Posted By: monkeyking
Date Posted: 08-Jun-2009 at 7:52pm
we were trying to find a function in devforce that can create our own entity as data binding source, but we can't find it. and we also tried to create a customized entity by ADO.net EF, but it seems too comlicated, because ADO.net EF doesn't have a mature feature to deal with that, all we must do is using XML to create, but if we use XML, it has some conflict with the original DB entities as they are going to share the same PK.



Posted By: kimj
Date Posted: 10-Jun-2009 at 7:47am
Originally posted by monkeyking

...so should we create our own databinding source manually?
Yes.  The ViewModel part of a Model-View-ViewModel should work for you. 
 
Originally posted by monkeyking

...or Devforce has a solution to deal with our problem.  
I think you've asked this question a few times, though more in line with retrieval.  DevForce does not have anything else to offer you than what's already been discussed.
 


Print Page | Close Window