Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
A LINQ lookup dilemma
Message
From
30/06/2008 17:20:17
 
 
To
30/06/2008 13:17:45
General information
Forum:
ASP.NET
Category:
LINQ
Miscellaneous
Thread ID:
01327573
Message ID:
01327746
Views:
8
Here's an updated screenshot of what I have built so for... http://www.jordanmachine.com/wpf_screenshot_2008_06_30_Vista.jpg

Ok, so it's pretty (maybe), BUT, when you "de-normalize" a data set (Linq-to-Sql) like this (the JobItems GridView), it's fine for presentation in a WPF ListView.GridView (non-editable), but how in the world could you ever host this de-normalized data set in a live-edit data grid or ContentControl designed for editing and then post back changes to the Sql Server?

Of course, you would design your UI so that only the non-lookup fields/columns would be editable, but the data set which I am presenting contains all fields in an ad-hoc class that I built just for presentation.

My Linq-to-Sql model doesn't even know about my ad-hoc class.

I'm not sure what I have built has any use beyond presentation.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform