Add-Migration fails on a UWP class library

[ryanwinter]

I moved my model to a class library (along with the context). When I try and run the command:

Add-Migration MyFirstMigration -project Model

I get the following error:

Add-Migration : Exception calling "CreateInstanceAndUnwrap" with "8" argument(s): "Could not load file or assembly 'Microsoft.Framework.Logging.Abstractions, Version=1.0.0.0, Culture=neutral, 
PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified."
At line:1 char:1
+ Add-Migration MyFirstMigration -project GymBuilder.Model
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Add-Migration], MethodInvocationException
    + FullyQualifiedErrorId : FileNotFoundException,Add-Migration

[natemcmaster]

(obvious question) Do you have "Microsoft.Framework.Logging.Abstractions" installed in this new project?

[emrs-jm]

I am having a similar issue. The difference is that I get the same error with a different exception listed:

Add-Migration : Exception calling "CreateInstanceAndUnwrap" with "8" argument(s): "Could not load type 'Microsoft.Data.Entity.Utilities.LazyRef`1' from assembly 
'EntityFramework.Core, Version=7.0.0.0, Culture=neutral, PublicKeyToken=null'."
At line:1 char:1
+ Add-Migration TestStart -project EM.Eligibility.EntityFramework -Context EmConte ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Add-Migration], MethodInvocationException
    + FullyQualifiedErrorId : TypeLoadException,Add-Migration

The migration system was creating migrations in beta5 and before with my context in a project containing my context alone. I initially thought that I had a dangling reference somewhere to beta 5, but that does not appear to be the case. The folders inside my packages folder for the solution include the following:

    EntityFramework.Commands.7.0.0-beta6
    EntityFramework.Core.7.0.0-beta6
    EntityFramework.InMemory.7.0.0-beta6
    EntityFramework.Relational.7.0.0-beta6
    EntityFramework.Relational.Design.7.0.0-beta6
    EntityFramework.SqlServer.7.0.0-beta6
    Ix-Async.1.2.4
    Microsoft.AspNet.Razor.4.0.0-beta6
    Microsoft.CodeAnalysis.Analyzers.1.0.0
    Microsoft.CodeAnalysis.Common.1.0.0
    Microsoft.CodeAnalysis.CSharp.1.0.0
    Microsoft.Framework.Caching.Abstractions.1.0.0-beta6
    Microsoft.Framework.Caching.Memory.1.0.0-beta6
    Microsoft.Framework.Configuration.1.0.0-beta6
    Microsoft.Framework.Configuration.Abstractions.1.0.0-beta6
    Microsoft.Framework.Configuration.Binder.1.0.0-beta6
    Microsoft.Framework.DependencyInjection.1.0.0-beta6
    Microsoft.Framework.DependencyInjection.Abstractions.1.0.0-beta6
    Microsoft.Framework.Logging.1.0.0-beta6
    Microsoft.Framework.Logging.Abstractions.1.0.0-beta6
    Microsoft.Framework.OptionsModel.1.0.0-beta6
    Newtonsoft.Json.7.0.1
    Remotion.Linq.2.0.0-alpha-004
    SharpZipLib.0.86.0
    System.Collections.Immutable.1.1.37-beta-23109
    System.Reflection.Metadata.1.0.21

Are there any packages in the list above that would make you think that I have a dangling reference to an older version of EF7?

in my context, the OnConfiguring is setup as follows:

protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
        {
            base.OnConfiguring(optionsBuilder);

            if (!optionsBuilder.IsConfigured)
            {
#if DEBUG
                optionsBuilder.UseSqlServer(@"Server=(localdb)\v11.0;Database=EligibilityTest;Trusted_Connection=True;"); 
#else
                // other default to go here.
                optionsBuilder.UseSqlServer(@"Server=(localdb)\v11.0;Database=EligibilityTest;Trusted_Connection=True;"); 
#endif
            }
        }

I am currently using VS2015 Enterprise in .Net 4.5.1 projects. Interestingly enough, in test code where I ensure that the database is created, it seems to create the database properly.

[ryanwinter]

I spent about an hour trying to figure this out. The package it is complaining about is pulled in as a dependency from EntityFramework.Sqlite. I actually manually added this to both projects and it still didnt work.

This was a brand new project that I created with a simple model. When I move the context to the main project everything works fine.

[natemcmaster]

Just by inspection, I'm not sure what is wrong. Can you create a project that reproduces this issue? Make sure to add the project.lock.json file so we can see exactly which packages are being used.

[emrs-jm]

I found what my issue was. Embedded in my project file it was referencing the old beta5 build. I had to remove it from a text editor since NuGet and Visual Studio weren't catching it.

You may want to double check the packages folder and make sure that the Microsoft.Framework.Logging.Abstractions folder is present with it's data for the beta version you are using.

[ryanwinter]

I uploaded a project that was causing my grief:
http://1drv.ms/1K6u2Gi

[natemcmaster]

Confirmed bug.

[ryanwinter]

Awesome, I'm not going insane.

[bricelam]

I got to the bottom of this. NuGet 3 (with project.json) no longer copies package assemblies to the output folder for class library projects by default. It's related to NuGet/Home#1084. We're working with the team to figure out a solution.