0
bryan created
First timer, so bear with me..
Can we propose to change the DateTime fields for Auditable entities to DateTimeOffset? that should help representing a very specific point in time
All libraries should be netstandard 2.0 at least to help with compatibility, any dependencies on libraries that include AbpNetZeroCore (which I believe has the License check code) needs to be built to .NET Core 2, is this possible or in the works?
Why not use .net core abstractions for Dependency injection, Logging and Configuration instead of using Castle abstractions? This is limiting for users which don't want to use Castle
1 Answer(s)
-
0
Hi,
- DateTimeOffset is not compatible with several database engines. As this is a framework it must cover as many as databases. So this is custom work for individual usage.
- AspNetZeroCore package can be set as netstandard-2.0, you can create an issue on GitHub for that to be trackable. (btw I forwarded this request)
- It was implemented before .net core abstractions package. For now, I don't think you can replace Castle, there's a tight coupling with Castle.Windsor. See the issue <a class="postlink" href="https://github.com/aspnetboilerplate/aspnetboilerplate/issues/288#issuecomment-71333978">https://github.com/aspnetboilerplate/as ... t-71333978</a>
