EF5 Release Candidate Available on NuGet

[アーティクル]
05/15/2012

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.

A couple of months ago we released EF5 Beta 2. Since releasing Beta 2 we have made a number of changes to the code base, so we decided to publish a Release Candidate before we make the RTM available.

This release is licensed for use in production applications. Because it is a pre-release version of EF5 there are some limitations, see the license for more details.

What Changed Since Beta 2?

This Release Candidate includes the following changes:

Added a CommandTimeout property to DbMigrationsConfiguration to allow you to override the timeout for applying migrations to the database.
We updated Code First to add tables to existing database if the target database doesn’t contain any tables from the model. Previously, Code First would assume that the database contained the correct schema if it was pointed at an existing database that was not created using Code First. Now it checks to see if the database contains any of the tables from the model. If it does, Code First will continue to try and use the existing schema. If not, Code First will add the tables for the model to the database. This is useful in scenarios where a web hoster gives you a pre-created database to use, or adding a Code First model to a database created by the ASP.NET Membership Provider etc.

This release also includes fixes for the following bugs found in Beta 2:

Exception in partial trust applications ‘Request for ConfigurationPermission failed while attempting to access configuration section 'entityFramework'.’
Migrations: Using a login that has a default schema other than ‘dbo’ for the user causes runtime failures
Migrations: DateTime format issue on non-en cultures
Migrations: Migrate.exe does not set error code after a failure
Migrations: Error renaming entity in many:many relationship
Migrations: Checking for Seed override fails in partial trust
Migrations: Better error message when startup project doesn't reference assembly with migrations
Migrations: ModuleToProcess deprecated in PowerShell 3 causes warning when installing EF NuGet package

What’s New in EF5?

EF 5 includes bug fixes to the 4.3.1 release and a number of new features. Most of the new features are only available in applications targeting .NET 4.5, see the Compatibility section for more details.

Enum support allows you to have enum properties in your entity classes. This new feature is available for Model, Database and Code First.
Table-Valued functions in your database can now be used with Database First.
Spatial data types can now be exposed in your model using the DbGeography and DbGeometry types. Spatial data is supported in Model, Database and Code First.
The Performance enhancements that we recently blogged about are included in EF 5.
Visual Studio 11 includes LocalDb database server rather than SQLEXPRESS. During installation, the EntityFramework NuGet package checks which database server is available. The NuGet package will then update the configuration file by setting the default database server that Code First uses when creating a connection by convention. If SQLEXPRESS is running, it will be used. If SQLEXPRESS is not available then LocalDb will be registered as the default instead. No changes are made to the configuration file if it already contains a setting for the default connection factory.

The following new features are also available in the Entity Model Designer in Visual Studio 11 Beta:

Multiple-diagrams per model allows you to have several diagrams that visualize subsections of your overall model.
Shapes on the design surface can now have coloring applied.
Batch import of stored procedures allows multiple stored procedures to be added to the model during model creation.

Getting Started

You can get EF 5 Release Candidate by installing the latest pre-release version of the EntityFramework NuGet package.

PM> Install-Package EntityFramework –Pre

These existing walkthroughs provide a good introduction to using the Code First, Model First & Database First workflows available in Entity Framework:

We have created walkthroughs for the new features in EF 5:

Compatibility

This version of the NuGet package is fully compatible with Visual Studio 2010 and Visual Studio 11 Beta and can be used for applications targeting .NET 4.0 and 4.5.

Some features are only available when writing an application that targets .NET 4.5. This includes enum support, spatial data types, table-valued functions and the performance improvements. If you are targeting .NET 4.0 you still get all the bug fixes and other minor improvements.

Support

We are seeing a lot of great Entity Framework questions (and answers) from the community on Stack Overflow. As a result, our team is going to continue spending more time reading and answering questions posted on Stack Overflow.

We would encourage you to post questions on Stack Overflow using the entity-framework tag. We will also continue to monitor the Entity Framework forum.

Entity Framework Team

License.rtf

Comments

Anonymous
May 15, 2012
Do you know what the ETA is for a version of WCF Data Services that works with an EF5 with Enums model? Right now if you have an EDMX with Enums and you point it at a WCF Data Services 5 service, the whole thing fails at the metsdata level, because EnumType is a legitimate EntityType on .NET 4.5.
Anonymous
May 15, 2012
gooooooooooooooooooooooooooooood
Anonymous
May 15, 2012
The comment has been removed
Anonymous
May 15, 2012
@xjpepit What version of NuGet do you have installed? You probably want to update to the latest.
Anonymous
May 15, 2012
Install-Package EntityFramework -IncludePreRelease
Anonymous
May 15, 2012
Thanks all, I've re-installed the NuGet latest version and got EF5.0 now.
Anonymous
May 15, 2012
Thank you, But I really hope to see TVF supporting code-first in the next version. I have been waiting for several months now for this feature to come.
Anonymous
May 15, 2012
Hi Guys, Any chance you can fix/provide a workaround for this problem: www.pabich.eu/.../Entity-Framework-migrations-donrsquot-support-parallel-development.aspx
Anonymous
May 16, 2012
The comment has been removed
Anonymous
May 16, 2012
Any chance to make it open source? data.uservoice.com/.../2858489-make-it-open-source
Anonymous
May 17, 2012
@Robert - the enums support in WCF DS is definitely the most popular ask right now (data.uservoice.com/.../1012609-support-enums-as-property-types-on-entities). We are very focused on other priorities at the moment (a more efficient wire format, integrating our tooling support with NuGet, better support for containment) but will hopefully address enum support soon.
Anonymous
May 17, 2012
Since DbContext is recomended API and will replaced ObjectContext what is the future of STE?
Anonymous
May 17, 2012
The comment has been removed
Anonymous
May 17, 2012
@Sławek Rosiek - Our team isn't planning to make any significant investments in the STE template at this stage. Our recommendation for new applications would be to make use of a technology like WCF Data Services or Web API for N-Tier scenarios. We will continue to support folks using the STE template though.
Anonymous
May 17, 2012
Is it worth it to use EF5 on an app that targets .NET 4.0 and uses model-first? Is there a detailed changelog?
Anonymous
May 17, 2012
Repeating the same question David Romero asked. Considering performance improvments, Is it worth it to use EF5 on an app that targets .NET 4.0 ?
Anonymous
May 17, 2012
Are conventions customizable yet?
Anonymous
May 17, 2012
@Joshua: Customizable conventions us a very popular request. It is not in EF5, but certainly in the list for our next version.
Anonymous
May 17, 2012
@Ashraf, David: EF5 contains bug fixes that apply independently of what version of .NET you are using, and for that reason it is worth upgrading to EF5 anyway. Sorry we currently don't have a detailed log.
Anonymous
May 17, 2012
For TVFs in Code First, is it possible to emulate what EF5 is generating? In other words, could we use the designer to generate the designer code for this and copy it into our Code First DbContext? Or is this truly DB first only?
Anonymous
May 18, 2012
@Kamran: EF5 has the ability to map TVFs in an EF model. Once mapped, an application can use TVFs in LINQ to Entities queries. The main difficulty is that mapping of TVFs is only supported in XML metadata artifacts, e.g. in EDMX files used by the EF Designer. Code First still lacks the necessary API to produce mappings that include functions and stored procedures, therefore even if you copied the code we produce for TVFs in the DbContext-based code generation it wouldn't work. Besides that, TVFs are defined in the database using the native language of the database. EF might be able to use a TVF but what goes in the body of a TVF is completely opaque to EF. In the future, when we enable Code First to produce mappings for stored procedures and functions you will still have to provide the definition of the TVF, e.g. by writting CREATE FUNCTION SQL statements in your migration scripts. In the meanwhile the only way to use TVFs in a Code First application is through the SqlQuery method, which allows materializing objects out of native SQL queries but doesn't premit any complicated mapping or composability using LINQ to Entities.
Anonymous
May 19, 2012
I have updated EntityFramework in my project and after that database initializes stopped working, in my case it is class that inherited from CreateDatabaseIfNotExists. Were any changes are made in the new version related database initializes?
Anonymous
May 19, 2012
@Dmitry Fisenko: We have not seen this issue but yours may be a case we haven't considered. Could you please use the "Email Blog Author" link to get in contact with us? We might need a repro project and more information about your database server configuration in order to investigate.
Anonymous
May 21, 2012
What is the approximate final release date for EF5?
Anonymous
May 21, 2012
Good job on the part about it adding tables to an existing database. One thing that I liked about NHibernate better than Entity Framework was that you can make it drop and create the tables in a database rather than dropping and creating the database itself. I liked this better because if you had other things in the database such as users, they wouldn't be lost.
Anonymous
May 22, 2012
Great work on this release, I have a few questions regarding enum support:-

Is there a way to declare a Description for my enum values ? via T4 template ?
I'm working on a large scale application, is there a way to import enum's without having to add them individuallly via the 'Convert to Enum' process?

Anonymous
May 23, 2012
@Alexandr Mihalciuc – We don’t have an exact date yet, EF5 is included in a number of places in Visual Studio 11 so it will definitely be available by the final release of Visual Studio 11. Depending on the number of bug reports etc.but we may make the release available on NuGet before then.
Anonymous
May 25, 2012
@Lombo - This isn't supported in the designer at the moment but we do have an item on our backlog to enable it. This won't be available in this release though. For the moment you may want to just define the enum in a separate code file. You can specify the enum type that you create as the ExternalType in the properties window for the enum type in the Entity Designer. If you are using the DbContext code generator then the enum will no longer get generated. If your using the default code generation you would need to add the T4 templates and modify them to no longer generate the enum because they don’t honor the ExternalType property yet.
Anonymous
May 25, 2012
Thanks Rowan, appreciate your response
Anonymous
May 26, 2012
i found something strange in EF 5.0 RC. I upgraded my solution to this version and now I get a strange error which might be a bug. I have the following EntityTypeConfiguration: public class SiteMapping : EntityTypeConfiguration<Site> { public SiteMapping() { // doing some Mapping here } } I then call the following generic function in order to register this EntityTypeMapping: public MapEntity<TEntity>(EntityTypeConfiguration<TEntity> configuration) { _modelBuilder.Configurations.Add(configuration); } This gives me the following error: Object of Type "SiteMapping" cannot be converted to Type "System.Data.Entity.ModelConfiguration.EntityTypeConfiguration'1[Site]" This is stragen because SiteMapping is derived from EntityTypConfiguration<Site>. This used to work perfectly in EF4.x!! Were there some changes regarding this in EF5.0 and do you have some hints how to solve this problem?? Thank you very much for your support!!
Anonymous
May 26, 2012
sorry! Problem solved! I forget to update one reference to the new EntityFramework.dll Best Regards!
Anonymous
May 29, 2012
since .NET 4.5 drop support for windows XP and Vista, there is no way to use new features :( (in real world)
Anonymous
May 30, 2012
The comment has been removed
Anonymous
May 30, 2012
@Dimentox - This looks like a bug that we've recently fixed (the fix will be included in the final RTM of EF5), the issue is likely caused by having an unloaded project in your solution.
Anonymous
May 30, 2012
@Dimentox: another temporary workaround you might want to try is to explicitly set the -StartUpProjectName parameter in the enable-migrations command. There is an issue in the version of PowerShell contained in Windows 8 previews that causes this exception in the code we use to resolve the start up project.
Anonymous
May 31, 2012
Why are you guys using an incorrect naming format for all of your types like DbMigration? It should be DBMigration. Two letter abbreviations should be capitalized. You're teaching everyone bad habits. The Microsoft conventions are long standing and should be observed: msdn.microsoft.com/.../ms229043.aspx Please understand that these things are important.
Anonymous
May 31, 2012
@James Patterson. There are four reasons for this. First, many types in the .NET Framework that have existed for a long time (DbConnection, DbDataReader, and so on) use the Db prefix. We decided that being consistent with most existing types in the Framework was worthwhile. Second, Db is not really an abbreviation for database. It's just a prefix we use to group related classes together. It doesn't indicate that all of these classes are directly related to the database, but rather that they are part of the DbContext family of APIs, and DbContext is part of the wider ADO.NET family. Third, the Framework guidelines talk about "acronyms". Now the definition of an acronym can be debated but an argument can and has been made that DB is not an acronym because database is not two words. This can clearly also be argued the other way. Fourth, Most people on the team prefer the way Db looks. We wouldn't use this as the sole reason for choosing it, but combined with the other arguments it did play a part.
Anonymous
June 01, 2012
Hi, Does this version works with the Visual Studio 2012 RC? The EDMX Designer does not open and throws a exception. There is a workaround/fix for this? Or should we wait for a new compilation of EF5. Thank you in advance.
Anonymous
June 01, 2012
This version is in fact compatible with Visual Studio 2012 RC. If you are having issues with the EF Designer in Visual Studio 2012 RC I believe it must be a separate issue. What is the exception you are getting? Have you had any previous beta versions of VS or the EF June 2011 CTP installed in your machine?
Anonymous
June 01, 2012
Hi Arthur, “First, many types in the .NET Framework that have existed for a long time (DbConnection, DbDataReader, and so on) use the Db prefix. We decided that being consistent with most existing types in the Framework was worthwhile.” Most types in the FCL adhere to the two letter convention. Yes there are some Db prefixed types, but they are others that do not DBNull, DBDataPermission. Using Db instead of DB is perpetuation of an unfortunate oversight. “Second, Db is not really an abbreviation for database. It's just a prefix we use to group related classes together. It doesn't indicate that all of these classes are directly related to the database, but rather that they are part of the DbContext family of APIs, and DbContext is part of the wider ADO.NET family.” I doubt we could find any developer that would take Db as not being short for database. “Fourth, Most people on the team prefer the way Db looks. We wouldn't use this as the sole reason for choosing it, but combined with the other arguments it did play a part.” That’s because you guys have grown used to it. But it’s still inconsistent. I can tell you that it stands out as being wrong from my point of view, and I’m sure I’m not the only one. At the heart of the issue, I don’t like Db because it teaches new devs that that’s how you format abbreviations. It’s a shame because the convention is important as it allows you to distinguish between a real word and an abbreviation. You guys can’t change it now. I'm passionate about C# and the conventions that go with it, so from my point of view I see it as a broken window.
Anonymous
June 02, 2012
The comment has been removed
Anonymous
June 03, 2012
@MartinFr - it sounds like you have "breaking when a CLR exception is thrown" option. Go to the Debug -> Exceptions menu (Ctrl + D, E) and make sure that the checkbox in the "thrown" column is unchecked for CLR exceptions. There are a few exceptions that may be thrown when database does not exist but they are handled so there is no need to break on them.
Anonymous
June 05, 2012
Pawel: Thanks. I wish it was that easy. But it is not the case, all are unchecked. It also happens when not using IIS Express but running in IIS. I have to keep trying to refresh (or step through the exceptions if debugging), until the database is finally recreated, and then it starts working, until it needs to recreate the database again. Very frustrating and pretty much impossible to work with in the long run.
Anonymous
June 05, 2012
please add zip download. Nuget have proxy problem. cannot download.
Anonymous
June 05, 2012
I can't find the Table attribute as well as the notmapped attribute???
Anonymous
June 06, 2012
Any help? stackoverflow.com/.../entity-framework-5-0-entityobject-generator-not-available-in-visual-studio-2012
Anonymous
June 06, 2012
@Paul Marvin: I have replied on the StackOverflow thread. In summary: we are working on updated templates that should become available in the VS gallery/online tab shortly.
Anonymous
June 06, 2012
@Cyril: we used to define these data annotations in EntityFramework.dll, but in .NET 4.5 those annotations were moved to System.ComponentModel.DataAnnotations.dll proper. In the process they were also moved to a new namespace: System.ComponentModel.DataAnnotations.Schema. If you just add this as a using/import statement in your code file this should help. Sorry for the inconvenience.
Anonymous
June 06, 2012
@MartinFr: Any chance you could provide a repro project for us to look at? Either clicking "Email Blog Author" or posting to StackOverflow.com and posting a link to the thread would do.
Anonymous
June 06, 2012
I can't for the life of me, get enums working as detailed in this post & the code-first walkthrough (using VS2012 + EF5 + .NET4.5). Are they actually working now, or do we still have to wait for the final EF release to get this feature?
Anonymous
June 06, 2012
@Shane Hancock: They are already working with the combination of EF5 + .NET 4.5 pre-release versions. Is this enums walkthrough what you are referring to?: msdn.microsoft.com/.../hh859576. Are you getting some sort of exception?
Anonymous
June 07, 2012
Hello Has the case sensitive foreign key issue has been resolved?
Anonymous
June 07, 2012
@Diego B Vega: Yes, that's the walkthrough i'm referring to and no I'm not getting any exceptions. It behaves just like older versions of EF in that it simply ignores any properties that use an enum data type. I'm using code-first. Here's the question I raised about this on the forum y'day that contains some example code: social.msdn.microsoft.com/.../6326f515-ebe5-4fe0-b5d6-161560b755b0
Anonymous
June 07, 2012
@Shane Hancock: I have responded in the forum thread. You are using a nested enum type in your code snippet. EF doesn't currently support mapping to nested types (classes or enums). Moving the enum type defintion outside the class should make it work. This is a limitation we are looking into removing in the future. I will make sure your sample snippet is added in the bug we use to track this.
Anonymous
June 07, 2012
I searched the whole web and can not find an example where: The Entity Framework works with two databases on the same server. Could you please help me? It would be great to have an example.
Anonymous
June 08, 2012
@Matt F - Which particular issue are you referring to? @isNIL - Mapping one context to tables from two different databases is not supported. You could conceivably create views in one database that expose the tables from the other database, but that's going to be pretty messy. The best option is to define two contexts, one that maps to each database.
Anonymous
June 08, 2012
Why is it taking sooooooooo long to release the RTM???
Anonymous
June 10, 2012
The comment has been removed
Anonymous
June 10, 2012
The comment has been removed
Anonymous
June 10, 2012
@MartinFr: Not sure this will help, but one thing that usually keeps the database open is the Server Explorer window in VS. Another relatively common occurrence is that the application contains code that manages the connection lifetime manually (i.e. as opposed as leaving it for EF to manage the connection automatically) and it is also missing a call to DbContext.Dispose().
Anonymous
June 10, 2012
@Khaled - EF5 is integrated in Visual Studio 2012 in a number of places (for example the MVC project template includes the EF5 NuGet package). This means we need to take time to work with those teams to make sure the RTM package plays nicely with their product. The RC release does have a go-live license on it, so you can use it in production until RTM is available (check the license for more details).
Anonymous
June 11, 2012
@Rowan Miller I have a problem where foreign keys are case sensitive, and associated objects will not be loaded if the case does not match. Assume 2 tables. The first one is called Individual, with an ID of type varchar as primary key. Second table is called Address, that has a foreign key linked to the individual table. if the individual ID is "abc123" , but in the address table it is "ABC123" , the load of the Individual object will have a null Address object. If i change the foreign key value in the address table to "abc123" , then it creates the associated object on load. Also, I cannot "fix" the data and make all of the cases match.
Anonymous
June 13, 2012
@MattDFowler - That issue hasn't been addressed in EF5. We do have it on our backlog to look at for the next release though.
Anonymous
June 13, 2012
@Rowan Miller - Being able to query multiple databases with a single EF context seems like a reasonable thing to ask for. It's currently possible to query and join across multiple databases with LINQ to SQL simply by prefixing the database name to the table name in the .dbml (ie db1.dbo.table1, db2.dbo.table2) when a table isn't in the default database (ie initial catalog on the connection string). Is there a similar workaround in EF? If not there should be, otherwise it prevents cross-database queries that are otherwise possible in raw SQL and LINQ to SQL.
Anonymous
June 13, 2012
@Rowan Miller Thanks for responding, I have been looking for information about this. Is there a recommended work around for the case sensitive foreign key situation?
Anonymous
June 14, 2012
The comment has been removed
Anonymous
June 18, 2012
The comment has been removed
Anonymous
June 19, 2012
Hi, i have problem with changing nonullable property to nullable property. Database migration doesn`t detect this change and i must cheange database my self.
Anonymous
June 20, 2012
@MattDFowler - There isn't a good workaround at the moment, given 'fixing' the data is out you'd need to make it look like the data is 'fixed'. You could use a view that standardizes the casing. If you're working in the Designer you could also use a defining query, but that's not supported in Code First yet.
Anonymous
June 20, 2012
@victoralameda - What action are you performing when you see this error?
Anonymous
June 20, 2012
@Lisaj - I'm not able to reproduce this issue, in my example I had an 'int' property that I changed to 'int?' (same as Nullable<int>) and Migrations correctly generated an AlterColum. Can you provide some more details of the issue you are hitting?
Anonymous
June 20, 2012
Hi Will EF be available for Windows Phone 7 at some point? If you try it now you'll get the following error: "You are trying to install this package into a project that targets 'Silverlight,Version=v4.0,Profile=WindowsPhone71', but the package does not contain any assembly references that are compatible with that framework. For more information, contact the package author." I wanted to use EF for use with a local sqlce database on the phone, but it's not doable at the moment :/
Anonymous
June 25, 2012
@Martin Nyhjem - EF can't be used in WP7 applications. Our recommended approach is to use something like WCF Data Services/Web API/RIA to perform service based data access. Something like this article - msdn.microsoft.com/.../hh527719
Anonymous
June 25, 2012
Please fix the issue with checking whether a column value is null or has a particular value. E.g., in the Where clause: (x.ConcurrencyLockDate.Equals(null) || x.ConcurrencyLockDate < maxLockTime) results in the following SQL: ([Extent1].[ConcurrencyLockDate] < @p__linq__1) thanks
Anonymous
June 27, 2012
Erro ENUM: System.NotSupportedException: The enum or spatial property 'TIP_ENDERECO' on type 'END_PESSOA' cannot be mapped. Use DbModelBuilderVersion 'V5_0' or later to map enum or spatial properties.
Anonymous
June 27, 2012
@isNIL: Enum and spatial types work only if you are using Visual Studio 2012 and .NET Framework 4.5. You also need to make sure that your app is targeting .NET Framework 4.5
Anonymous
June 28, 2012
Any news about when will EF support TVF in code first?? We need an approximate date, URGENTLY.
Anonymous
July 05, 2012
The comment has been removed
Anonymous
July 08, 2012
Mapping of private property "as DDD requirement" will be supported?
Anonymous
July 08, 2012
@isNIL - You can map private properties using configuration classes (Fluent API) by nesting the configuration class inside the entity class. There are also various other approaches that folks have blogged about if you don’t want to nest configuration classes inside your entity classes, here is one example - www.codewrecks.com/.../mapping-private-properties-with-ef-4-1-rc-and-fluent-mapping
Anonymous
July 08, 2012
Rowan, Very good, would have the same version for VB, please?
Anonymous
July 09, 2012
@isNIL – I don’t have a post written in VB.NET but you could run it through a tool like this to convert it www.developerfusion.com/.../csharp-to-vb
Anonymous
July 09, 2012
Rowan, thank you....
Anonymous
July 17, 2012
Hi, I have a EF4.0 project using VS2010. Recently I have installed .NET 4.5 framework (release candidate) onto the web server but I haven't upgraded my build machine (ie. project is still built in .Net 4.0, VS 2010) After installing .NET 4.5, I noticed a change in query generation for TPT inheritance e.g. it is no longer joinning to the children tables when I'm only interested in information in the base class. I also seem to see improvement when the same query is run repeatedly. I thought what I see are improvements included in EF5. So I'm confused, am I still using EF4.0 or am I now using EF 5 just by upgrading to .NET framework to 4.5? I'm keen to know will there be further performance benefits for me to upgrade my project to EF5? and will I need to build my project in VS2011 or VS2012 targetting .NET4.5 to see further improvements? Ideally I would like to get the max performance gain of EF 5 with minimum change to my current set up. Thanks.
Anonymous
July 19, 2012
The comment has been removed
Anonymous
July 22, 2012
Hi. I'm under the impression that EF5 with WCF Data Services throws an exception because the EntityFramework.dll in the lib/net45 folder was compiled against .net4.0 instead of .net4.5 Can anyone confirm me this? Thanks.
Anonymous
July 22, 2012
Sorry. Let me rephrase. I was refering to supporting Enum Types. I'm under the impression that EF5 with WCF Data Services throws an exception --- regarding the use of Enum types --- because the EntityFramework.dll in the lib/net45 folder was compiled against .net4.0 instead of .net4.5 Can anyone please confirm me this? Thanks.
Anonymous
July 22, 2012
The comment has been removed
Anonymous
July 22, 2012
@Pawel: I already had tried without enums and it had worked. I can't antecipate why should the Data Services be that restrictive. What puzzled me, by inspecting the reference to EntityFramework.dll, was the runtime value: Path = ...EntityFramework.5.0.0-rclibnet45EntityFramework.dll Runtime Version = v4.0.30319
Anonymous
July 22, 2012
The comment has been removed
Anonymous
July 22, 2012
@Pawel: Thanks! I forgot about that. I thought it was a all new runtime.
Anonymous
July 29, 2012
Any support for Unique Constraints and Relationships yet?
Anonymous
July 30, 2012
@Rob – No, not in EF5. Our team currently isn't planning to implement it for the next version either, you can vote on the feature here - entityframework.codeplex.com/.../299.
Anonymous
July 30, 2012
What .net 4.5 technology are you using to get the performance improvements, more specifically, why are they not possible in .net 4.0?
Anonymous
July 30, 2012
The comment has been removed
Anonymous
August 03, 2012
Have posted a question here stackoverflow.com/.../ef-migrations-migrate-exe-generate-script which i'm struggling to get an answer to. Any help on when / if this feature will arrive? Thanks.
Anonymous
August 08, 2012
@Greg - Brice from our team has followed up on the Stack Overflow thread.
Anonymous
August 08, 2012
Spotted the response - thanks very much for coming back.

次の方法で共有