-
Notifications
You must be signed in to change notification settings - Fork 166
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
Refactor to segregate EntityFramework dependencies #8
Comments
Thanks for the suggestion. Unfortunately, I have no time to dedicate to changing this project in the manner you suggest. |
Since I’ve already done it, do you want it? From: Scott Smith [mailto:[email protected]] Thanks for the suggestion. Unfortunately, I have no time to dedicate to changing this project in the manner you suggest. — |
Feel free to submit a pull request. I can't say if I will/can take it. It all depends on the impact to everyone else using it. At least if I see what has changed, I can make an informed decision. |
Closing as no response |
I have found this project extremely useful. However, I was unable to use the nuget package because of the way that the dependencies are packaged.
I'm integrating into an SOA product with very strict rules, in particular data access dependencies may not occur in a business service, only in a data service. To solve this issue, I cloned your repository and divided it into two assemblies LinqKit and LinqKit.EntityFramework. This solved my issue, and others may have the same requirement. I would suggest this to be your default, and update the nuget package accordingly.
The text was updated successfully, but these errors were encountered: