EntityFramework Storage implementation (draft)

[semack]

Hi @valdisiljuconoks,

This pull-request related to #59 includes:

1. Added ServiceLocator anti-pattern to the DbLocalizationProvider.AspNetCore implementation. It temporary there and can be removed after the redesign of TypeFactory to support DI.
2. Implemented DbLocalizationProvider.AspNetCore.EntityFramewrok storage library.
3. Modified AspNetCore example to use a new storage library.
4. Changed product version to 6.4.0.
5. Updated README.md

It needs to be tested now. Unfortunately, hadn't enough time for it. Will do on this weekend if get luck.

Please review. Any suggestions are appreciated.

Kind regards,
Andriy

[valdisiljuconoks]

Awesome! However v7 (next major) version is already in workings ;) I have few local branches across all submodules where I was experiencing with new features.

I'm gonna pull over some of the features from this PR this add EF option for v7. Merge everything as-is would be too much hustle as things have changed.

[semack]

Ok, my goal to start using your lib in my project ASAP ;)
The main change is adding ServiceLocator and its registration. The EF lib I've added is standalone, so it doesn't need any global modifications. Waiting for v7 ;)

[valdisiljuconoks]

Could you elaborate on service locator necessity? As in next major version I'm going to or at least I'm planning to throw out all the statics. It's been too much trouble in unit tests and concurrent things and all around

[valdisiljuconoks]

Anything particular you were missing from the library that should be supported out of the box?

[semack]

Could you elaborate on service locator necessity? As in next major version I'm going to or at least I'm planning to throw out all the statics. It's been too much trouble in unit tests and concurrent things and all around

It needs there to get an instance of DbContext registered in the application. After making lib the DI compatible, it could be injected by handler's or repository's constructor automatically in a classical way.

BTW, You could find my comments in TODOs I've added.

[semack]

Do you have any updates?

[valdisiljuconoks]

I've been crazy busy with my primary responsibilities, so I'm delaying behind here.

Working on v7 is in progress, but it has quite big scope therefore it might not come as quick as we would like to.

I'll see ar some point how to merge EF. Just need to block time for this.

[valdisiljuconoks]

Hey @semack

Could you please merge conflicts before we proceed here? Not sure why, but your repo shown as "unknown" from my perspective. Do you know reason?

[semack]

Could you please merge conflicts before we proceed here? Not sure why, but your repo shown as "unknown" from my perspective. Do you know reason?

Unfortunately, I've deleted my fork. Anyways, I guess you could do the review by yourself, nothing special has been changed.