Open asynts opened 4 years ago
I tried removing that but that was not enough, still the same issue. I got it running by doing grep -r adminpack
(Linux) and removing everything that had the word "adminpack" in it.
After removing it from the migrations it somehow worked, but I was very confused why this made a difference. If Entity Framework is presented with an empty database, it uses the dbcontext snapshot to initialize it, right? But removing it from there was not enough...
I am not sure when this was introduced but the build is currently broken:
I remember having a discussion somewhere, that some of the generated code referenced the "adminpack" extension somewhere. It is mentioned in some of the database migrations.
We should remove this from the migrations and find the cause of this issue.