Comments on: From PDC2009 Day 1: Entity Framework 4 http://rwandering.net/2009/11/17/from-pdc2009-day-1-entity-framework-4/ The blogged wandering of Robert W. Anderson Mon, 20 Jun 2011 16:33:27 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Robert W. Anderson http://rwandering.net/2009/11/17/from-pdc2009-day-1-entity-framework-4/comment-page-1/#comment-204562 Robert W. Anderson Thu, 19 Nov 2009 20:01:26 +0000 http://rwandering.net/2009/11/17/from-pdc2009-day-1-entity-framework-4/#comment-204562 I talked to someone today and found: There are designer improvements, particularly that model changes shouldn't get paved when refreshing the model. More major changes to help make the model more navigated are planned for the future (i.e., post .NET 4). Inserts? Aside from some small performance improvements, nope. The woman I spoke to basically asked, "how's that working out for you?" . . . she suggested that we bypass EF and use ADO.NET for the inserts instead. I wasn't able to find someone who knew the answer to the GUID / SEQUENTIALGUID questions I had. That doesn't sound promising to me, but I'll look further. I talked to someone today and found:

There are designer improvements, particularly that model changes shouldn’t get paved when refreshing the model. More major changes to help make the model more navigated are planned for the future (i.e., post .NET 4).

Inserts? Aside from some small performance improvements, nope. The woman I spoke to basically asked, “how’s that working out for you?” . . . she suggested that we bypass EF and use ADO.NET for the inserts instead.

I wasn’t able to find someone who knew the answer to the GUID / SEQUENTIALGUID questions I had. That doesn’t sound promising to me, but I’ll look further.

]]> By: Pandelis http://rwandering.net/2009/11/17/from-pdc2009-day-1-entity-framework-4/comment-page-1/#comment-204521 Pandelis Wed, 18 Nov 2009 02:10:32 +0000 http://rwandering.net/2009/11/17/from-pdc2009-day-1-entity-framework-4/#comment-204521 Most of these are glaring omissions in v1 (.NET 3.5) and will be much appreciated. It definitely seems like the current version was rushed out the door. This release addresses most of the quirks of v1 (for example no easy access to foreign keys). The ability to access native user defined functions on the database is big for me (because unlike stored procedures, they are composable), as is the ability to unit test without having to modify a database. Any info on designer improvements, or bulk inserts? Most of these are glaring omissions in v1 (.NET 3.5) and will be much appreciated. It definitely seems like the current version was rushed out the door. This release addresses most of the quirks of v1 (for example no easy access to foreign keys). The ability to access native user defined functions on the database is big for me (because unlike stored procedures, they are composable), as is the ability to unit test without having to modify a database.

Any info on designer improvements, or bulk inserts?

]]>