This project is read-only.


Creating 2 EDMXs from same DB causes 1st .tt file to "lose" nested classes


Create an EDMX called Model1.edmx from (say) Northwind importing all tables. You will create (amongst others) a file which will generate a .cs file for each entity Category.cs, Customer.cs etc.

Now create another EDMX called Model2.edmx from the same DB for the same tables. You will create But also generates Category.cs, Customer.cs etc.

But part of the codegen process is to nest the generated .cs files (Category.cs, Custoemr.cs etc) under This means that if you return to the only file now nested under that is Model1.cs. All the entity classes have been "moved" to be nested under
Closed Dec 13, 2016 at 8:32 PM by RoMiller
EF Team Triage: We are transitioning this project to GitHub ( As part of this transition we are bulk closing a large number of issues in order that our new issue tracker will accurately reflect the work that our team is planning to complete on the EF6.x code base.

Moving forwards, our team will be fixing bugs, implementing small improvements, and accepting community contributions to the EF6.x code base. Larger feature work and innovation will happen in the EF Core code base ( Closing a feature request in the EF6.x project does not exclude us implementing the feature in EF Core. In fact, a number of popular feature requests for EF have already been implemented in EF Core (alternate keys, batching in SaveChanges, etc.).

This is a bulk message to indicate that this issue was closed and not ported to the new issue tracker. The reasons for not porting this particular issue to GitHub may include:
  • It was a bug report that does not contain sufficient information for us to be able to reproduce it
  • It was a question, but sufficient time has passed that it's not clear that taking the time to answer it would provide value to the person who asked it
  • It is a feature request that we are realistically not going to implement on the EF6.x code base
    Although this issue was not ported, you may still re-open it in the new issue tracker for our team to reconsider ( We will no longer be monitoring this issue tracker for comments, so please do not reply here.


RoMiller wrote Aug 14, 2012 at 6:40 PM

We should at least make the file name unique.