Is there any way I can make Effort.EF6 work with a null database initialiser? about entityframework-effort HOT 7 CLOSED

Hi JonPSmith - Sorry for the late response. This shouldn't be a problem as Effort is not able to work when migrations is enabled, the suggested workaround is indeed to disable the initialiser.

What does happen if you indeed initialize your db explicitly?

from entityframework-effort.

Hi @tamasflamich,

The problem is if I call a null initialiser, e.g. Database.SetInitializer<MyDbContext>(null) then the next time Effort.EF6 accesses the database I get the exception I detailed in the first post above. I do this because some tests do access a real database directly and I want to make sure it doesn't look for migrations.

I have no migrations set on the database so its not that. I'm pretty sure Effort.EF6 doesn't support the calling of a null initialiser.

It would be great to have that fixed, but as a creator of a number of open-source libraries and working I know that time is limited. If you do get a chance to look at this/fix it then let me know.

from entityframework-effort.

@JonPSmith, I had a similar problem. I solved it by registering a System.Data.Entity.NullDatabaseInitializer<T> in my Dependency Injection container (Ninject, in my case) for production and the default System.Data.Entity.CreateDatabaseIfNotExists<T> initializer for unit tests. Then in the constructor of my EF context I just select whatever was registered, like so:
Database.SetInitializer(DIContainer.Get<IDatabaseInitializer<MyDbContext>>());

My use case isn't quite the same as yours since I don't have to think about migrations. But, you might consider a CustomInitializer for the tests that does the "Database.CreateIfNotExists()" line recommended in the error message and ignores any migration steps that the default initializer would try to do.

from entityframework-effort.

I'm having a similar issue, except my context is database first but with FluentAPI, so a hybrid model. My Context constructor always runs Database.SetInitializer<Context>(null);. That being the case, shouldn't Effort also apply this? I've tried putting it in my constructor, as well as in the unit test explicitly, however, I always get

Effort.Exceptions.EffortException: Database has not been initialized.

from entityframework-effort.

Hello @screaney ,

We will try to look at this issue next week,

Best Regards,

Jonathan

from entityframework-effort.

Any news on this?

I'm having the same issue, although calling context.Database.CreateIfNotExists() is not an option for me, because I use a custom initialization infrastructure.

from entityframework-effort.

Hello @michaelfoidl ,

Unfortunately no, we never found a solution.

The Effort in-memory database doesn't exist by default unlike your real database, so it currently requires the memory database to be created.

from entityframework-effort.