Alexnaldo wrote   I know NetTier, LLBLGen and many, many others ORM and I don't think a good idea create a new ORM... After many years studing, using and creating (http://www.codeplex.com/nanomapper) ORM I must to say that Microsoft Entity Framework have good concepts that solved many of commons problems of ORM. IMHO EF is the best to integrate with VWG application. , Alexnaldo Santos

Hi Alexnaldo,

It's not that I am trying to write my own ORM, It is a way of implementing the IModel interface in the case I am building. If I wanted to use something else, it is just a kind of wrapper class that is laying in between your application and the datalayer but implements IModel. The problem I have to resolve is that in no case I want any references to dataobjects or some kind of business objects. To do this I need to have create objects that are lightweight and have 'yet' no clue of what they are and need to do.

All that this framework will do is listen to the interfaces. If you would like to use Entity Framework I welcome you to write an class that lays between the Imodel and the dataobjects. But again in a  scaffolder you really have no need to have complete objects that you need to fill. As you dynamically create and present the data and functions. This in contrast to hand written screens. Here you might want to have a direct reference to your dataobjects and this is also valid. Because the screen will have a implemented interface of IForm and that way the framework will pull this screen in and present it to you with all its functions.

Just see every single object, control, presentation or form as a plug-in. if you don;t like it you throw it away and create your own. but I want it to be easy to this. Instead of writing a new ORM or standard I want to let the final implementor to be able to use their standards and tools. this is just a productivity booster in the sense of not having to think about 80% of the application but lets you focus on the more complex routines of processes.

I hope I can get through that I don't mind what tech anybody uses. I will allow any tech you want to use and I do an implementation based on Subsonic. but to be flexible I want to be able to configure objects that have calculated fields. That I externally can tell what rules apply for validation of an entity.

A Contact record in the database is exactly the same as if it was created with a generate DAL or any other ORM.
If somebody knows of what I am trying to tell please step in :-)
 

Hi Alexnaldo,

What exactly do you mean by a Projection?

LLBLGen supports all types of queries.  Including Linq, Scalar, flat DataTables, and of course, fetching EntityCollections.  It's Predicate filtering mechanism is extremely powerful; more powerful than Linq.  It also supports Projections, which allows you to export your Entities into any other format, including POC objects, etc.  What do you mean by Projections?

Ryan