da wir schon bei Nicht-Release-Produkten sind ... hier noch ein neues CTP-Produkt:
[Download details: Microsoft ADO.NET Entity Framework Feature Community Technology Preview 5]
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=35adb688-f8a7-4d28-86b1-b6235385389d
----------------------------------
Kopiert aus [Microsoft ADO.NET Entity Framework Feature CTP 5 Readme]
This is the list of new and improved features in CTP5:
DbContext API
-
Model-First and Database-First support:
New T4 templates is included for using DbContext/DbSet
-
Validation of objects on SaveChanges:
Validation is based on the use of Data Annotations and currently only supported in Code First
-
Change tracking API:
Allows you to access information and operations applicable to objects that are tracked by a DbContext
-
Access to Original, Current & Store Values
-
Entity state (i.e. Added, Unchanged, Modified, Deleted)
-
Explicit Loading: API to load the contents of a navigation property from the database
-
Databinding:
DbSet.Local exposes an ObservableCollection representing the local contents of the DbSet. This is particularly useful when performing databinding in WPF applications. The new ToBindingList extension method can be used to obtain a binding list for Windows
Forms applications.
-
No-Tracking Queries:
This can be achieved via the AsNoTracking extension method on IQueryable<T>.
-
DbContext Configuration:
Allows the following options to be configured for a DbContext instance:
-
Lazy Loading
-
Validate On Save
-
Auto Detect Changes
-
Raw SQL Query/Command execution:
Allows raw SQL queries and commands to be executed via the SqlQuery & SqlCommand methods on DbContext.Database. The results can optionally be materialized into object instances that are tracked by the DbContext via the SqlQuery method on DbSet.
-
Improved concurrency conflict resolution:
We have added better exception messages that allow access to the affected object instance and the ability to resolve the conflict using current, original and database values
-
DbContext.ObjectContext has moved:
Rather than being a protected member we have made the underlying ObjectContext available via an explicitly implemented interface, this allows external components to make use of the underlying context. Getting the context now looks like: ((IObjectContextAdapter)myContext).ObjectContext
-
Excluding EdmMetadata Table:
If Code First is generating your database and you wish to exclude the EdmMetadata table, this is now done by removing a convention (note that you do no longer need to do this when mapping to an existing database).
-
Types renamed in System.Data.Entity.Database namespace:
ciao Frank
