You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, I would like to thank you for your great job in this library.
I would like to ask you if it's possible to separate the Auditable and Trackable interfaces in a separate package and include this new package reference as a dependency to here?
I'm asking this because you did a great job in the interfaces and I would like to reuse them (as a package) in my "domain project layers" without having to add entity framework dependencies to projects that would probably not EF as ORM.
I'm aware of the #3, but since I'm only asking for the interfaces without the extensions, I guess that it would not escalate to lots of separate libraries.
For instance: Specification.cs only has dependencies from .NET Framework.
Hello!
First of all, I would like to thank you for your great job in this library.
I would like to ask you if it's possible to separate the Auditable and Trackable interfaces in a separate package and include this new package reference as a dependency to here?
I'm asking this because you did a great job in the interfaces and I would like to reuse them (as a package) in my "domain project layers" without having to add entity framework dependencies to projects that would probably not EF as ORM.
I'm aware of the #3, but since I'm only asking for the interfaces without the extensions, I guess that it would not escalate to lots of separate libraries.
For instance: Specification.cs only has dependencies from .NET Framework.
Other example: AuditableEntities.cs only have dependency to "System" package.
What do you think?
Thank you in advance!
Kind regards!
The text was updated successfully, but these errors were encountered: