Entity Framework Improvements in Visual Studio 2010 SP1
The information in this post is out of date.
Visit msdn.com/data/ef for the latest information on current and past releases of EF.
Today’s release of Visual Studio 2010 SP1 includes several performance and stability improvements for Entity Framework 4.0. MSDN subscribers can download the service pack immediately, and the release will have general availability on Thursday, March 10.
- Download Service Pack 1 (MSDN Subscribers)
- Thursday's general availability download is here .
Here’s what new in SP1 for Entity Framework:
Performance Improvements for Large Models
The most notable improvement is performance in the designer (or at the command-line using EDMGen.exe) when working with large models. In Visual Studio 2010, reverse-engineering a model from a medium to large database (>200 tables) would take an unnecessarily long time. With SP1, a large model (for example, 500 tables) can now be reverse-engineered within seconds.
Bug Fixes for Self-Tracking Entities
Edmxes and HandleCascadeDelete
Self-Tracking Entity Template fails to generate code for function imports that don’t have a return value
Entity does not get marked as modified when FK association is nulled via EntityReference.EntityKey
Miscellaneous code-generation changes to conform to VB pretty-lister guidelines
Template generates uncompilable code for dot-separated namespaces
Template doesn’t generate default values for scalar properties on complex types
Comments
Anonymous
March 08, 2011
Something's wrong with that "Today's release..." link at the top.Anonymous
March 08, 2011
thanks Kyralessa, should work nowAnonymous
March 08, 2011
Does sp1 have the ef code first bits baked in? Or is that still in futures?Anonymous
March 08, 2011
Travis: The code first and productivity improvements are not in VS 2010 SP1. See blogs.msdn.com/.../ef-4-1-is-coming-dbcontext-api-amp-code-first-rtw.aspx for more information.Anonymous
March 08, 2011
Hi, what about this bug: connect.microsoft.com/.../storegeneratedpattern-property-in-ado-net-entity-model-designer-sets-cdsl-annotation-but-not-ssdl-attribute It has been marked as fixed for a long time but still doesn't seem to be fixed in SP1? When can we expect to get this? It's crucial for us since we use a lot of database-generated IDs and computed columns.Anonymous
March 09, 2011
Hey Benny, Yes that fix is also included in SP1, thanks for pointing that out. We're going to update the post with a list of fixes for the EF designer as well. Thanks, JonathanAnonymous
March 09, 2011
I am trying to find a solution to the "AcceptChanges cannot continue because the object's key values conflict with another object in the ObjectStateManager" problem. I understand the cause of the error, I have an object graph pulled to the client via a wcf call. This object graph includes a collection created from a many-to-many relationship and these objects in this collection also are object graphs. The client makes a additional call via wcf to get another object graph to be added to the collection of the first object. I will then get the above error when I attempt to save this object if the objects now in the collection have a graph item in common. As a specific example: I have an AuctionSet that has a many to many relationship with AuctionItem (AuctionSet->AuctionSetAuctionItem<-AuctionItem). AuctionItem also has a relationship to Location (AuctionItem->Location). If I pull an AuctionSet and include the AuctionItems and AuctionItems.Location, and then pull an additional AuctionItem that includes Location and that Location is the same as one of the existing AuctionItems.Location I will get the above error. What is the correct way to prevent or deal with this? The Location list is large and it would be a problem to pull the entire list at the same time as the single AuctionSet. Thanks in advance for any direction. ShaneAnonymous
March 13, 2011
Is the order of install relevant between VS 2010 SP1 and EF 4.1 CTP 5? Thanks, Tim