Hi,

Im still working on how to work on a custom data access layer for Dynamic Data Site, and i downloaded the Dynamic Data 4.0 Preview 3 and played around with it.im so interested in it.

mean time i was searching some other ways and came across with this nice post http://blogs.msdn.com/davidebb/archive/2008/06/18/using-asp-net-dynamic-data-with-objectdatasource.aspx (thank you sir..for this nice post!!) that demos how to use ObjectDataContext which talks to your business layer class. (this approch also states there are limitations where it can cater only the DataContext and ObjectContext and should support LINQ)

So im interested to know what are the major changes we see in DomainDataSource apart from it can talk to DomainService class.

Also, if we were to have a completly different DAL(non-ObjectContext and non-DataContext) with DataReaders and etc... can we build up a full scaffolding site just by registering the DomainService class with the Dynamic Data engin? I feel inorder to make dynamic data scaffolding we need to have a ObjectContext or a DataContext in place...  what if we dont have either, how will that be possible?

Thank you very much,

Dilrukshi

Have a look at Nikhil Kothari's video at MIX09 where he put DomainService through it's paces with Silverlight and uses other things than Linq and DataContext.