I'm finding some limitations in Core class libraries, in my case using EF Core migrations. There are tutorials around about how to fake libraries to behave as apps, but I can't tell if this is an architectural decision about class libraries going forward, or just a temporary fix while the EF team finishes up the missing functionality. Will tooling such as migrations be available for class libraries later on?
TIA!
Dennis