Last post Jul 22, 2016 06:59 AM by NishantMittal
Jul 21, 2016 04:26 PM|sgude1|LINK
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?
Jul 21, 2016 04:37 PM|anurajp|LINK
There is no announcement related to this. But there is an issue in github EF Repo - https://github.com/dotnet/cli/issues/2645 And it is marked as a known issue in documentation - https://docs.efproject.net/en/latest/miscellaneous/cli/dotnet.html#preview-2-known-issues Hopefully
it will be fixed in the upcoming releases.
Jul 21, 2016 04:45 PM|sgude1|LINK
Yes, I've seen that thread, but it's mostly focused on hacks to make it work now. I can put my stuff in folders in the web project right now and split it out later if someone like Rowan Miller has said "this will arrive", but if it won't, then Core isn't
for my project.
Jul 22, 2016 06:59 AM|NishantMittal|LINK
Just want to share my experience when I did migration of my project from 2010 to 2015.I am using EL in my 2010 project and we also using Caching functionality regarding the same.But in Latest version of EL we don't have Caching. We have to use System.Runtime.Caching.
So it will be great in case any we will get Migration tool.