EF 6.1.1 Beta 1 Available

發行項
05/20/2014

Today we are pleased to announce the availability of EF6.1.1 Beta 1. This patch release includes a number of high priority bug fixes and some contributions from our community.

What’s in Beta 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:

Where do I get the beta?

The runtime is available on NuGet. Follow the instructions on our Get It page for installing the latest pre-release version of Entity Framework runtime.

The tooling for Visual Studio 2012 and 2013 is available on the Microsoft Download Center.

Support

This is a preview of changes that will be available in the final release of EF6.1.1 and is designed to allow you to try out the new features and report any issues you encounter. Microsoft does not guarantee any level of support on this release.

If you need assistance using the new features, please post questions on Stack Overflow using the entity-framework tag.

Thank you to our contributors

We’d like to say thank you to folks from the community who contributed features, bug fixes, and other changes to the 6.1 release:

What’s next?

All the changes we plan to include in the final release of EF6.1.1 are included in this Beta. If additional high priority bugs are reported on the Beta we will consider fixing them prior to the final release. Depending on the bug reports we get, we may provide another preview before the final release.

Comments

Anonymous
May 20, 2014
For me, the main enhancement ia about Any() query generation, specially inside Where(x=> x.Related.Any()) where it generates 4 sub queries instead of one
Anonymous
May 22, 2014
Hi Felipe, I think that you are referring to the improvement to the translation of Any() resulting from this contribution: entityframework.codeplex.com/.../6199. Could you please confirm that this is working for you better in the beta? It is hard to tell from your comment whether you are describing the previous behavior or the new one.
Anonymous
May 23, 2014
Hi all, Since the EF is the core of my solutions, before trying the new patch I would like to know if the "Designer: Error opening EF5 edmx with decimal precision in EF6 designer" fix addresses also the bug re-introduced on the Designer when editing the EF 4.0 version of edmx models or is it only about EF5 models? Thank you Alberto
Anonymous
May 27, 2014
@Alberto - Are you asking if the same issue is fixed for models created with EF4? If so, the answer is yes. If you are asking if a different bug has been fixed, could you provide details on the issue you are seeing so we can check.
Anonymous
May 30, 2014
Thank you very much Rowan! You understood perfectly: I was asking if the same bug was fixed for the EF4.0 models too. Going to try the update immediately Thank you again Alberto
Anonymous
June 05, 2014
I don't know if an old bug where property changed event handlers were not being raised for navigation properties when INotifyPropertyChanged was implemented in the data models. I don't know if I'm doing something wrong, or if this "bug" is still there: connect.microsoft.com/.../entity-framework-navigation-properties-don-t-raise-the-propertychanged-event Back then the EF team had written: "Thank you for this feedback. Unfortunately the product team cannot fix this issue in time for the upcoming Visual Studio 2010 release, but this has been prioritized highly for the next release of the Entity Framework in .NET. Thanks, Jeff Entity Framework Team"
Anonymous
June 05, 2014
Ignore my last post... I was using SelectedValueBinding instead of SelectedItemBinding (DataGridComboBoxColumn). Now property change notifications are being raised properly for the navigation property.
Anonymous
June 06, 2014
@James Portelli - Glad to hear it is working for you.
Anonymous
June 09, 2014
The issue "Designer: Error opening EF5 edmx with decimal precision in EF6 designer" still remains after I installed the update. Has anyone else experienced the same problem?
Anonymous
June 09, 2014
To clarify on my previous post, I may not be using EF5, since I don't have .tt files in my project. I do know that the "specified cast is not valid" issue started appearing after updating VS2013 to Update 2. The header of my edmx files starts like this: <?xml version="1.0" encoding="utf-8"?> <edmx:Edmx Version="3.0" xmlns:edmx="schemas.microsoft.com/.../edmx">  <edmx:Runtime>  <edmx:StorageModels> <Schema .... ... </edmx:Edmx>
Anonymous
June 09, 2014
@Victor De Cerqueira - You mentioned Update 2, this fix isn't included in Update 2. You'll need to download the separate installer (details are in the post). The EF6.1.1 tooling will be included in the next update for VS.
Anonymous
June 09, 2014
Rowan, I did install the update (beta version of EF 6.1.1), but the problem still persists. I was simply giving you a background of my scenario prior to first encountering the issue. Thanks!
Anonymous
June 10, 2014
@Victor De Cerqueira - Thank you for clarifying. Would you be able to open an issue on our CodePlex site and include an example of the model that is still encountering the issue with the EF6.1.1 tools installed? entityframework.codeplex.com/.../Create
Anonymous
June 10, 2014
Rowan, I just created a ticket in CodePlex and included a sample model. Thanks for providing the link and good luck working this issue out! Victor
Anonymous
June 12, 2014
My issue is resolved...I had installed the runtime, but not the tooling - duh! ;-)
Anonymous
June 12, 2014
@Victor De Cerqueira - Glad to hear it is resolved, thanks for following up.
Anonymous
June 17, 2014
Will we get the PDBs/Source this time via Symbol/Source Server for 6.1.1 RTM?
Anonymous
June 26, 2014
@Andre.Ziegler - We we're still blocked by an issue with Symbol Source. I've just moved the work item back onto our triage list to see if we are unblocked now.

共用方式為