none
ErrorGeneratingOutput EF 6.1 RRS feed

  • Question

  • Upgraded a MVC project to EF 6.1.  in VS 2012 using Nuget

    Installed the EF 6.1 Tools: http://www.microsoft.com/en-us/download/details.aspx?id=40762

    Now when I build the project The MyEntities.cs and the MyEntities.Context.cs file contains only:

    ErrorGeneratingOutput

    So the build fails.

    The VS110COMNTOOLS environment variable points to the correct path.
    I also completely deleted the edmx and recreated by build model from db; No change.


    • Edited by chuck02323 Monday, April 28, 2014 7:25 PM
    Monday, April 28, 2014 7:23 PM

All replies

  • When did VS2012 start working with EF 6? I know about EF 6 working with VS2013.
    Tuesday, April 29, 2014 1:43 AM
  • Hello chuck02323,

    What is your original Entity Framework? What model are you using, database first or code first?

    As far as I know, if we want to upgrade our MVC project from EF 5 to EF 6, we just need to install the EF6 by using Nuget. We does not need this tool in actual, the Tool is just used to give us additional choice.

    Do you have a try to create a new MVC project installing the EF6 directly rather than upgrading from EF 5(maybe) to EF 6 to see whether it will work since I create a MVC project in VS2012, and then upgrade it from EF5 to EF6 and build it successfully, even installing the tool?

    And please check if you are under this scenario:

    http://forums.asp.net/t/1949811.aspx?Error+building+an+entity+model+tt+is+empty+with+one+line+ErrorGeneratingOutput

    The code generator is looking for the missing DLLs in the following locations when using EF6 T4 template.

    Regards.


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Tuesday, April 29, 2014 3:05 AM
    Moderator
  • We couldn't get vs 2013 to work with TFS 2010.

    So we're trying ef 6 with 2012.  Because its not part of nuget or vs anymore you have to search for new stuff and installation instructions with google.

    http://forums.asp.net/t/1950055.aspx?Upgrading+MVC+and+razor+disaster

    http://msdn.microsoft.com/en-us/data/upgradeef6

    http://www.microsoft.com/en-us/download/details.aspx?id=40762

    Tuesday, April 29, 2014 1:16 PM
  • Original was 5, then 6 then 6.1.

    You do need to install the EF tools or 6.1 won't work.

    I deleted and then rebuilt the edmx by reverse engineering the db.

    Still got errors. Delete both tt  files. Compile again then it works.

    EF upgrades/revisions are a disaster. Always have been.  Probably always will.  Poor documentation, poor notifications, poor integration.

    http://forums.asp.net/t/1950055.aspx?Upgrading+MVC+and+razor+disaster

    http://msdn.microsoft.com/en-us/data/upgradeef6

    http://www.microsoft.com/en-us/download/details.aspx?id=40762


    • Edited by chuck02323 Tuesday, April 29, 2014 1:22 PM
    Tuesday, April 29, 2014 1:21 PM
  • We couldn't get VS 2013 to work with TFS 2010.

    You can always get TFS 2012 or 2013 Express. They are free. I have TFS 2012 Express working with VS2010 Pro, VS2012 Web and Desktop Express  and VS2013 Pro. It could be a stop gap measure for you. I have it on my personal Windows 8 Pro development machine. The Express edition supports up to 10 concurrent connections.

    https://www.dreamspark.com/product/product.aspx?productid=76 

    I remember I had to install what in the link for VS2010 Pro that was using TFS Express 2012 to use TFS. You can't add projects to TFS through VS2010. I had to go to VS2012 or 2013 to do that. But you can check-in and check-out code in VS2010 that was connected to TFS2012.

    Maybe, there is a patch out there for VS2013 to TFS2010 or you can look into the free TFS Express editions as a stop-gap measure.

    There is always a way to skin the cat, and if I were you, you should make your way back to using VS2013 with EF 6 and MVC 5  and not on some update basis but build solutions from scratch.

    Tuesday, April 29, 2014 2:16 PM
  • I have 30 developers on tfs.  As a VS 2013 tfs fix MS support said to reinstall vs 2013 to get TFS to work.  I don't think having 30 people reinstall 2013 would do anything other than waste time.

    Tuesday, April 29, 2014 2:36 PM
  • Well, did you try what MS suggested? Have you taken a machine that had no VS of any kind installed on the machine, installed VS2013 and tried to connect to TFS? 

    No, I would have any problems telling 30 developers to do a reinstall if I knew that would fix the problem - no problem whatsoever. :)

    Tuesday, April 29, 2014 2:46 PM