abpframework / abp Goto Github PK

• Create a view engine to find views in assemblies.

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

• User app service: CRUD for users including their roles. Also unit tests.
• Role app service: CRUD for roles. Also unit tests.
• Rename Abp.Identity to Abp.Identity.Domain.
• Create Abp.Identity.Domain.Shared dll and move consts and enums here.
• Add data annotation properties to Dtos.

Similar to ABP1 notification system.
Real time system will be implemented by SignalR Core.

• Entity
• Value object
• AggregateRoot

Create a localization system based on AspNet Core's new localization system: https://docs.microsoft.com/en-us/aspnet/core/fundamentals/localization,

See also https://docs.microsoft.com/en-us/aspnet/core/fundamentals/portable-object-localization

Note that we will introduce ILocalizationStore and implement it in EFCore/MongoDb/... (ORM) packages and make them optional

TODO/NOTES

• WithCulture.
• Javascript API (similar to current ABP)
• IHtmlLocalizer

• 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.

• Should be injectable, rather than a static instance.
• Check if AspNet Core or MS provides such an abstraction.

• Data filtering abstraction.
• Implement data filtering using EF Core 2.0.
• Implement filters for MemoryDb.
• Integrate to multitenancy data filtering.
• Implement soft delete.

Like in ABP1.

• Implement it like ABP 1.x
• Use it to create Ids for Identity Entities.

Should support;

• Each dbcontext can have different connection string. (uses default if not wanted)
• Implement module-name / database-name logic to be used on conn string resolving.
• On database per tenant, each tenant can have different connection string. (uses same db if not wanted)
  together in multitenancy.

Make logging works with a real logger, like log4net or serilog.

• AbpServiceBase
• ApplicationService
• DomainService

• Begin/Commit/Rollback unit of work which can contain multiple database connection and/or multiple dbcontext
• Support multiple ORM in a UOW.
• Implement UOW via EF Core

Like in ABP1. But also;

• Abstraction: IObjectMapper
• AutoMapper integration as default mapper: AutoMapperObjectMapper
• Allow to register special mapper classes per object-to-object (IObjectMapper<TSource,TDestination>), which overrides default mapper if defined.

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

Converted to a new project: https://github.com/aspnetzero/abp/projects/3

Use it to configure ABP and modules.

IDistributedEventBus abstraction

• Publishes events

LocalDistributedEventBus

• Publishes events using IEventBus

RabbitMQ Integration

• Implements IDistributedEventBus and publish events to RabbitMQ
• Receive events of RabbitMQ, dispatches them to subscribers, acknowledges the message then.

Like in ABP1.

see also: https://docs.microsoft.com/en-us/aspnet/core/fundamentals/host/hosted-services?view=aspnetcore-2.1

• DbContext and migrations
• Store implementation and registration (stores are in domain, and uses repositories)

General Requirements

• Ensure that ambient UOW scope works properly.
• Nested unit of works.
• Should be lazy. That means actually it does nothing until a real database operation is needed.
• Pass HttpContext.RequestAborted to UOW.Complete automatically.

AspNet Core Middleware & ActionFilter

• Should be located just before UseMvc() as a middleware.
• Reservation option to reserve a started UOW for later usage. Reserved by middleware and obtained by action filter.
• UOW Action filter should be able to work without middleware too.
• Should allow ActionFilter to control UOW properties (like istransactional, transaction isolation level etc)
• Should allow to rollback UOW without throwing exception.
• Should allow exception filter to rollback uow/transaction on error.
• Middleware completes the transaction/uow if no rollback and no error.
• What if we have exception on razor view execution..?
• If we have an exception on commit stage in the middleware, we should handle it as just like in ActionFilter, so client side gracefully handle it.

EF Core

• Create unit test with SQLite in memory.
• Create unit test with multiple dbcontextes (with same connstring) share same transaction.

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.

• Get CurrentTenant from IMultiTenancyManager while resolving connection string.

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.

• Load modules beginning from startup module
• Integrate to AspNet Core Startup class
• Make running in a Console application
• Load plugin modules

This feature is essential for a SaaS application.

Permission based authorization

• Implementation
• Unit Tests
• Policy integration
• Multitenancy
• Caching

• A module / database access object (like DbContext for EF) can declare a database name.
• Get module specific connection string using database name. Design it to easily be used with other database api providers.

• Entities
• Managers

• Create repository abstraction (IRepository, IQueryableRepository)
• Implement with EF Core

• Create tenant id access/change

Integrate to AutoFac and test with it.

• Abstractions.
• Default job manager.

Create an abstraction to create objects. As fallback, it uses Activator.CreateInstance.

like in ABP1. But should consider web farm scenarios better. Create AspNet Core SignalR implementation.

As similar to ABP1.

Setting Manager

• Get settings
• Set settings
• Extensibility (chain of resp. pattern)

Setting Definition Properties

• Name
• DefaultValue
• VisibleToClients
• IsInherited
• Custom Data