![]() Next: It appears that there's no simple way to set a FK field value on an associated object without re-querying the database. Two, I'm working SQLCE 3.5 and I'm using identity pk's.which I rudely found out are not supported by EF: Example: Make a FK field nullable, and the designer doesn't pick up (after a schema update) that the relationship should now be a 0.1 instead of 1. One, the designer is still not up to snuff. I've finally had a chance to take EF 4.0 for a spin, and I can say without a doubt, it's still a pile of junk compared to the alternatives. I'm sure you guys will eventually get it right. I'm not trying to put down EF, or the EF team's efforts. ![]() I just can't really see why Microsoft with all its resources, can't provide a more comprehensive solution than a very small company (or NHibernate for that matter) on its 4th (at minimum) attempt. I've also noticed in the EDMX's Designer source file where the entities are generated, that no metadata about the underlying storage is made available programmatically. I have to use a string to specify the 'eager' loading.really? That's terrible, not compile-time checkable, etc. ![]() Licenses = (from license in db.Licence.Include("") where =CategoryId select license).ToList() At home however, I'm just messing around with EF (still in VS2008/.NET 3.5 SP1) and at minimum, the following "smells" to me: NET 4 projects before moving to 2010), so we've settled on LLBLGen for the moment. I should state that I haven't looked at EF 4.0 yet (we're waiting for Expression Blend to support VS 2010. I just don’t know what the point of the Entities Framework is. Many people today choose LINQ to SQL for simpler projects or where there are more inexperienced developers, or they choose NHibernate (or something that sits on top of) for the more complex scenarios (and in combination with Spring.NET). NET 4.0 so that you could have produced something worth using. NET 3.5 SP1 was a massive mistake and should have been pushed back until. The ship has really sailed for the Entities Framework, the release made in. It would not hurt Microsoft to pay for development of a plugin to Visual Studio to support NHibernate based development and to perhaps put some money into NHibernates development for it to improve far beyond anything the Entities Framework will ever be. What I would like to see as a user of both NHibernate and LINQ to SQL, is Microsoft to open up the LINQ to SQL provider mechanism so that database vendors can implement support, and Microsoft get over its Not Invented Here syndrome and kill the Entities Framework and put its backing behind NHibernate. On the other hand you have a good simple ORM in LINQ to SQL that works well out of the box for a lot of scenarios, has good support in Visual Studio and is much more widely used (and written about) but only supports SQL Server. On one hand you are trying to push the Entities Framework, but as has been said a few times in this video it only really supports a few scenarios, it has serious constraints in relation to stored procedures, lazy loading, caching and poor Visual Studio support. After watching this presentation I feel that Microsoft really does not have it in them to do a full blown ORM.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |