New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove Entity Framework dependency. #376

Closed
kavics opened this Issue May 30, 2018 · 0 comments

Comments

Projects
None yet
3 participants
@kavics
Copy link
Contributor

kavics commented May 30, 2018

We have an Entity Framework dependency because of two reasons:

  1. In the StorageContext class, there is a solution for an Entity Framework problem ([see the line in the source], this should be removed.
    var instance = System.Data.Entity.SqlServer.SqlProviderServices.Instance;
  2. In the Providers class we instantiate the EF6SecurityDataProvider by a custom constructor that takes the connection string and timeout parameters.

Options

  • remove the Entity Framework dependency from the sensenet main component and use only where it is needed (e.g. SenseNet.Security). How to solve the instantiate with connection string problem?
  • replace EF6 with an in-memory solution as the default and let devs configure the EF solution if needed.
  • replace EF6 provider with the EFCore provider? (framework --> standard)

@kavics kavics added this to the Sprint 167 milestone Sep 6, 2018

@kavics kavics assigned kavics and unassigned kavics Sep 6, 2018

@tusmester tusmester self-assigned this Sep 6, 2018

@kultsar kultsar modified the milestones: Sprint 167, Sprint 168 Sep 19, 2018

@kultsar kultsar closed this Sep 26, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment