EF 6.1.2
EF6.1.2 is mostly about bug fixes, you can see a list of the fixes included in EF6.1.2 on our CodePlex site.
We also accepted a couple of noteworthy changes from members of the community:
    ·Query cache parameters can be configured from the app/web.configuration file
    <entityFramework>  
      <queryCache size='1000' cleaningIntervalInSeconds='-1'/>  
    </entityFramework>        
    ·SqlFile and SqlResource methods on DbMigrationallow you to run a SQL script stored as a file or embedded resource.
The runtime is available on NuGet. Follow the instructions on our Get It page for installing the latest version of Entity Framework runtime.
The tooling for Visual Studio 2012 and Visual Studio 2013 is available on the Microsoft Download Center. You only need to install the tooling if you want to create models using the EF Designer, or generate a Code First model from an existing database.

EF 6.1.1
You can see a list of the fixes/changes included in EF6.1.1 on our CodePlex site. In particular, we’d like to call out the following two fixes to issues that a number of people have encountered:
    ·Designer: Error opening EF5 edmx with decimal precision in EF6 designer
    ·Default instance detection logic for LocalDB doesn't work with SQL Server 2014
The runtime is available on NuGet. Follow the instructions on our Get It page for installing the latest version of Entity Framework runtime.
The tooling for Visual Studio 2012 and Visual Studio 2013 is available on the Microsoft Download Center. You only need to install the tooling if you want to create models using the EF Designer, or generate a Code First model from an existing database.

EF 6.1
This minor release adds the following features to EF6:
    ·Tooling consolidation provides a consistent way to create a new EF model. This feature extends the ADO.NET Entity Data Model wizard to support creating Code First models, including reverse engineering from an existing database. These features were previously available in Beta quality in the EF Power Tools.
    ·Handling of transaction commit failures provides the CommitFailureHandler which makes use of the newly introduced ability to intercept transaction operations. The CommitFailureHandler allows automatic recovery from connection failures whilst committing a transaction.
    ·IndexAttributeallows indexes to be specified by placing an [Index] attribute on a property (or properties) in your Code First model. Code First will then create a corresponding index in the database.
    ·The public mapping API provides access to the information EF has on how properties and types are mapped to columns and tables in the database. In past releases this API was internal.
    ·Ability to configure interceptors via the App/Web.config file allows interceptors to be added without recompiling the application.
    ·System.Data.Entity.Infrastructure.Interception.DatabaseLoggeris a new interceptor that makes it easy to log all database operations to a file. In combination with the previous feature, this allows you to easily switch on logging of database operations for a deployed application, without the need to recompile.
    ·Migrations model change detection has been improved so that scaffolded migrations are more accurate; performance of the change detection process has also been enhanced.
    ·Performance improvements including reduced database operations during initialization, optimizations for null equality comparison in LINQ queries, faster view generation (model creation) in more scenarios, and more efficient materialization of tracked entities with multiple associations.
The runtime is available on NuGet. If you are using Code First then there is no need to install the tooling. Follow the instructions on our Get It page for installing the latest version of Entity Framework runtime.
The tooling for Visual Studio 2012 and Visual Studio 2013 is available on the Microsoft Download Center. You only need to install the tooling if you want to use Model First or Database First.

EF 6.0.2
The 6.0.2 patch release is limited to fixing issues that were introduced in the EF6 release (regressions in performance/behavior since EF5).
The 6.0.2 patch includes fixes to some performance and functional issues that were introduced in the 6.0.0 and 6.0.1 releases. You can view a full list of the issues on our CodePlex site.
The runtime is available on NuGet. If you are using Code First then there is no need to install the tooling. Follow the instructions on our Get It page for installing the latest version of Entity Framework runtime.
The tooling for Visual Studio 2012 and Visual Studio 2013 is available on the Microsoft Download Center. You only need to install the tooling if you want to use Model First or Database First.

EF 6.0.1
The 6.0.1 patch release is limited to fixing issues that were introduced in the EF6 release (regressions in performance/behavior since EF5). This is a runtime only release ( available on NuGet), there was no update to the tooling.
The most notable changes were to fix some performance issues during warm-up for EF models. This was important as warm-up performance was an area of focus in EF6 and these issues were negating some of the performance gains made in EF6.
You can see a complete list of the individual fixes in this patch on the EF CodePlex site.

EF 6
This release can be used in Visual Studio 2013, Visual Studio 2012 and Visual Studio 2010 (runtime only) to write applications that target .NET 4.0 and .NET 4.5.
Tooling
The EF6 Tooling is included in Visual Studio 2013 and available for download for Visual Studio 2012. See the Get Entity Framework page for more information.
The focus for the tooling in EF6 was to add support for the EF6 runtime and to enable shipping out-of-band between releases of Visual Studio.
The tooling itself does not include any new features, but most of the new runtime features can be used with models created in the EF Designer.
Runtime
The EF6 runtime can be installed from NuGet. See the Get Entity Framework page for more information.
The following features work for models created with Code First or the EF Designer:
·Async Query and Saveadds support for the task-based asynchronous patterns that were introduced in .NET 4.5.
·Connection Resiliencyenables automatic recovery from transient connection failures.
·Code-Based Configuration gives you the option of performing configuration – that was traditionally performed in a config file – in code.
·Dependency Resolutionintroduces support for the Service Locator pattern and we've factored out some pieces of functionality that can be replaced with custom implementations.
·Interception/SQL logging provides low-level building blocks for interception of EF operations with simple SQL logging built on top.
·Testability improvements make it easier to create test doubles for DbContext and DbSet when using a mocking framework or writing your own test doubles.
·DbContext can now be created with a DbConnection that is already opened which enables scenarios where it would be helpful if the connection could be open when creating the context (such as sharing a connection between components where you can not guarantee the state of the connection).
·Improved Transaction Support provides support for a transaction external to the framework as well as improved ways of creating a transaction within the Framework.
·Enums, Spatial and Better Performance on .NET 4.0 - By moving the core components that used to be in the .NET Framework into the EF NuGet package we are now able to offer enum support, spatial data types and the performance improvements from EF5 on .NET 4.0.
·Improved performance of Enumerable.Contains in LINQ queries.
·Improved warm up time (view generation), especially for large models.
·Pluggable Pluralization & Singularization Service.
·Custom implementations of Equals or GetHashCode on entity classes are now supported.
·DbSet.AddRange/RemoveRange provides an optimized way to add or remove multiple entities from a set.
·DbChangeTracker.HasChanges provides an easy and efficient way to see if there are any pending changes to be saved to the database.
·SqlCeFunctions provides a SQL Compact equivalent to the SqlFunctions.
The following features apply to Code First only:
·Custom Code First Conventions allow write your own conventions to help avoid repetitive configuration. We provide a simple API for lightweight conventions as well as some more complex building blocks to allow you to author more complicated conventions.
·Code First Mapping to Insert/Update/Delete Stored Procedures is now supported.
·Idempotent migrations scripts allow you to generate a SQL script that can upgrade a database at any version up to the latest version.
·Configurable Migrations History Table allows you to customize the definition of the migrations history table. This is particularly useful for database providers that require the appropriate data types etc. to be specified for the Migrations History table to work correctly.
·Multiple Contexts per Database removes the previous limitation of one Code First model per database when using Migrations or when Code First automatically created the database for you.
·DbModelBuilder.HasDefaultSchema is a new Code First API that allows the default database schema for a Code First model to be configured in one place. Previously the Code First default schema was hard-coded to "dbo" and the only way to configure the schema to which a table belonged was via the ToTable API.
·DbModelBuilder.Configurations.AddFromAssembly method allows you to easily add all configuration classes defined in an assembly when you are using configuration classes with the Code First Fluent API.
·Custom Migrations Operations enabled you to add additional operations to be used in your code-based migrations.
·Default transaction isolation level is changed to READ_COMMITTED_SNAPSHOT for databases created using Code First, allowing for more scalability and fewer deadlocks.
·Entity and complex types can now be nestedinside classes.

EF 5
This release can be used in Visual Studio 2010 and Visual Studio 2012 to write applications that target .NET 4.0 and .NET 4.5. When targeting .NET 4.5 this release introduces some new features including enum support, table-valued functions, spatial data types and various performance improvements.
If you create a new model using the Entity Framework Designer in Visual Studio 2012, the EF5 NuGet package will be installed to your project and the generated code will make use of EF5. New ASP.NET projects created in Visual Studio 2012 (including MVC projects) also have the EF5 NuGet package installed by default.
The Entity Framework Designer in Visual Studio 2012 also introduces support for multiple-diagrams per model, coloring of shapes on the design surface and batch import of stored procedures.

EF 4.3.1
This patch release included some bug fixes to the EF 4.3 release and introduced better LocalDb support for folks using EF 4.3 with Visual Studio 2012.

EF 4.3
The EF 4.3 release included the new Code First Migrations feature that allows a database created by Code First to be incrementally changed as your Code First model evolves.

EF 4.2
This release includes bug fixes to the EF 4.1.1 release.
Because this release only included bug fixes it could have been the EF 4.1.2 patch release but we opted to move to 4.2 to allow us to move away from the date based patch version numbers we used in the 4.1.x releases and adopt the http://semver.org standard for semantic versioning.

EF 4.1.1
In addition to bug fixes this patch release introduced some components to make it easier for design time tooling to work with a Code First model. These components are used by Code First Migrations (included in EF 4.3) and the EF Power Tools.
Note the NuGet package for this release has the version number 4.1.10715. We used to use date based patch versions before we decided to adopt the http://semver.org standard for semantic versioning.

EF 4.1
The EF 4.1 release was the first to be published on NuGet. This release included the simplified DbContext API and the Code First workflow.
Note the NuGet package for this release has the version number 4.1.10331. We used to use date based patch versions before we decided to adopt the http://semver.org standard for semantic versioning.

EF 4
This release was included in .NET Framework 4 and Visual Studio 2010. New features in this release included POCO support, lazy loading, testability improvements, customizable code generation and the Model First workflow.
Although it was the second release of Entity Framework it was named EF 4 to align with the .NET Framework version that it shipped with. After this release we started making Entity Framework available on NuGet and adopted semantic versioning since we were no longer tied to the .NET Framework Version.

EF (or EF 3.5)
The initial release of Entity Framework was included in .NET 3.5 SP1 and Visual Studio 2008 SP1. This release provided basic O/RM support using the Database First workflow.

上一篇: Entity Framework 6连接Sqlite数据库示例
下一篇: WinForm快速调整控件Tab键顺序
文章来自: Version History
引用通告: 查看所有引用 | 我要引用此文章
Tags:
最新日志: