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!!!!!!!!!!