tracker-enabled-dbcontext
tracker-enabled-dbcontext copied to clipboard
bilal-fazlani
EntityFramework 7 / EF Core support?
Do you have plans for supporting upcoming EF7/Core? I'm writing a new application, and would like to both use the newest EF version (even though it's still a pre-release) and also all the power of your audit/tracking.
I suspect it may need to be an entirely different project/repository. I can't imagine the entity framework internals are similar enough to make this an easy port.
The tracker-enabled-dbcontext code itself should port easily from what I've seen. The real issue will be updating the EntityFramework.MappingAPI project on which the former depends. I may look at this if I don't have an alternative by the time Core goes RTM. On Mar 28, 2016 8:28 AM, "Patrick Michalina" [email protected] wrote:
I suspect it may need to be an entirely different project/repository. I can't imagine the entity framework internals are similar enough to make this an easy port.
— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/bilal-fazlani/tracker-enabled-dbcontext/issues/94#issuecomment-202439908
Started to look into auditing for EF Core, found this project and was wondering what is the current status? If there is already a fork for core, I would be interested in trying it out, even if pre-alpha since core is now officially 1.0.
There is no work done .. or even started yet for migrating this to EF core. Not sure right now if it should be a new project or a port....
Also there is no EF7. Its EF Core 1.0 EF will continue to progress from 6.1.3 to 6.2 and so on.. And EF core will start from 1.0
having said that I don't know if porting this library to EF core 1.0 is the right way, we might need a separate project for EF core 1.0
Hi, I was searching for entity audit/tracking libs, and found this one. Seams a good solution, but I definitely need a EF Core + identity version.
Do you have an ETA for a first alpha version I can give a try ?
Maybe a new project in the same repo can be a good idea. Also, you can pack the lib as one nuget package, with different binaries and dependencies for each framework profile.
