Microsoft Entity Framework vs EntitySpaces

For a new project, will you recommend EntitySpaces vs Microsoft Entity Framework?

If yes, could you provide reasons please?

Sure,

1. You can get up and running with ES in weeks. (IMO: You need a degree for the Entity Framework)
2. ES is not based on reflection, the Entity Framework is (ES is faster)
3. ES is much easier to customize (and about to be dramatically easier in the next release) .
4. The Entity Framework is driven off of LINQ, but LINQ is not serializable (not easily and when it is - its HUGE!). ES supports LINQ, but, IMO, their API is much better to use. IDid I mention that it is substantially better to serialize?
5. ES responds to issues from their customers like no other. Microsoft still hasn't even addressed a simple issue like binding to an enum (as far as I know a simple task liek the enum issue should have been addressed in weeks - it was years and - nada). You get rapid support here; you get a big forum with the Entity framework, where issues go to a committee and then get passed on to who knows where and before it is resolved, they change something that kicks it back to the beginning, and then a years later it is still swirling around as a problem).
6. Look up the forums with the Entity Framework for issues related to N-Tier or Distributed applications. The responses will tell you why I think you need a degree with the Entity Framework.

ES works! ES is fast! ES supports N-Tier applications. ES supports serialiation. ES is about to go into the stratosphere when hey implement the "layered" approach to customization.

 If you can't tell, there is only one recommendation that I would offer.

 

 

Professor Trevor sold it. 

ES rocks and 2009 will bring it "full circle" in my opinion

The product is awESome!!!!!!!!!!

Trevor, this post seems to echo your comments to the "T"

Why you should not use the ADO.NET Entity Framework

 

BTW: I am finishing up a degree in Accounting and I have to leave my project development and then return some time later.

I have discovered that leaving ES projects and returning is really not hard to do. This is a really big statement (in my view). For those that don't know, I contributed substantially to competing products. There really is nothing like ES - nothing even close.

Having bragged so much (which ES deserves), I would suggest something for the stage after the 'layered templates'. I expect nothing any time soon, but do want to contribute or suggest based on feedback I sense in realation to competing products (yes, I am still involved with other products - that is life).

Currently, ES builds from an existing database and it does not get involved in creating/updating database structure. If I could have my dream, ES would support defining, in the simplest manner possible, objects/tables/relationships where ES could actually build the database.

Then I would want the ability to populate default data. That ability is actually here now, but I would want some streamlined/super efficient efficient means to do so.

Then the next stage would be the ability to provide a before snapshot of a database structure and an after snapshot of database structure and be able to run scripts that populate the new database from the old... actually I think its best if a database is copied with all the data and then the tables that are changed/added/modified run through a migration engine... but this final dream (I suspect) would be some time off.

 I hope you guys don't go... WHAT?, WTF?

 I wouldn't change how ES has focused development for noth'n, I am just sharing my dream of beyend the short-term. Let me remind everyone... I am patient; although, my drool cup is getting really full for the 'layered templates'.