This framework provides to the application developers the following functionalities (among others).
To use this framework just include the packages you need in your project and go.
It is composed by the following components provided as NuGet packages.
Technical documentation can be found here: Kpok Patagon Framework class library.
The core component and the root of all other packages.
The data component that allows the development of domain model objects, data services, ORM and more, in a database agnostics way, so the code can be used for any database engine.
This package provides components that transparantly allows the developer to store application data in a MySql database.
This package provides components that transparantly allows the developer to store the application data in an Oracle database.
This package provides components that transparantly allows the developer to store the application data in a SQLite database.
This package provides components that transparantly allows the developer to store the application data in a Microsoft Sql Server database.
This package provides services to generate and process data model modification auditing information.
The cache component that allows the development to store data in a service cache that can store information in memory or in a Redis cache.
This package provides common models and services usefull for develop CLI applications.
This package provides common components, domain object models, their data services, a numerator and a parameter service, usefull for many applications.
This packages provides common models usefull for many applications.
Provides components for multi-tenenat applications.
Provides components for building Asp.Net web applications.
Provides components for multi-tenant Asp.Net web applications like model binders, tenant providers and more.
You develop an application by creating class libraries that will contain the application business logic, data model objects and data services.
This class library will reference (at a minimum) the core and the data component, this will made the application database agnostic.
Then you will create a web application (or other kind: UWP, Console, etc.) for the user interface and within this (the deployable binaries) you will include the components for the database to use (Oracle or Sql Server, etc.) and use the IoC container to inject an appropiate set of components according to the actual environment.
From the home page of this documentation explore the framework topics like configuration, domain object models, data services, ORM, etc. or see the technical documentation.
samples
directory for samples of how to use this framework.
In this document