View Code? Open in Web Editor
NEW
Open-source web application framework for ASP.NET Core! Offers an opinionated architecture to build enterprise software solutions with best practices on top of the .NET. Provides the fundamental infrastructure, cross-cutting-concern implementations, startup templates, application modules, UI themes, tooling and documentation.
Home Page: https://abp.io
License: GNU Lesser General Public License v3.0
C# 76.48%
CSS 0.42%
PowerShell 0.32%
JavaScript 5.12%
Batchfile 0.01%
HTML 9.03%
Dockerfile 0.03%
Shell 0.02%
Smarty 0.01%
TypeScript 8.06%
Go 0.10%
SCSS 0.31%
Less 0.08%
abp's People
abp's Issues
IDistributedEventBus abstraction
LocalDistributedEventBus
RabbitMQ Integration
like in ABP1. But should consider web farm scenarios better. Create AspNet Core SignalR implementation.
General Requirements
AspNet Core Middleware & ActionFilter
EF Core
Use it to configure ABP and modules.
Permission based authorization
Specifications
It will be the application layer which will contain application services for Abp.Identity.
It can be able to be consumed as REST style remote API.
It can be used as services to be injected by a 3-layer MVC application controllers.
It can be deployed as a microservice.
Should be developed based on #53
Functionality
Make logging works with a real logger, like log4net or serilog.
Similar to ABP1 notification system.
Real time system will be implemented by SignalR Core.
Setting Manager
Setting Definition Properties
Requirement
We need interception for two purposes;
Cutting Edge code
Especially needed for non-web projects. Because, they can be done via AspNet Core filters in a web project.
Auditing
Authorization
Unit of work
Validation
Dynamic proxying
Dynamic c# proxies to call remote methods
Ideas
Veawing
Mono.Cecil: Best performance, independent, supports .NetStandard (it's still beta). Hard to implement.
Fody: Does not support .NetStandard and probably will not be in a short time.
DynamicProxying
Rely on Castle Windsor (which does not support .NetStandard yet) for AutoFac. It's also DI framework depended.
TODO: Seach for alternatives.
Should be injectable, rather than a static instance.
Check if AspNet Core or MS provides such an abstraction.
Should be more and easier extensible, by extension methods?.
It should work by claims by default.
By default, it will only contain UserId. TenantId, Impersonator informations, organization units... should all be extensions.
This feature is essential for a SaaS application.
Create an abstraction to create objects. As fallback, it uses Activator.CreateInstance.
Requirement
We need to able to use different implementations for same service per tenant. Autofac support it. We may provide a way to select a service implementation based on the current tenant name.
Functionality
Log all requests just like in old ABP.
Log all entity changes just like in old ABP.
Additional
logs can be sent to different destinations (like to elastic search...).
Audit log module will have its own dbcontext and layers.
Allow to easier contribute to audit logging.
Also investigate this project: https://github.com/thepirat000/Audit.NET
Integrate to AutoFac and test with it.