ova.NetCore.Common.EntityFramework.Abstraction 1.6.1.19

EntityFramework

This solution is designed for easy creation database and development of any application by ASP NetCore EntityFramework in one-context SQL infrastructure. The solution implements abstraction, infrastructure, configuration and initial levels.

The product serves for:

• implementation of entities using the IEntity and INavigation interfaces;
• building a database schema using entity configuration files;
• automatic creation of instances of entities using entity configuration files;
• creation of a new database in case of its absence;
• initialization of database tables using separate json files, if necessary.

Solution contents

• main interfaces: IEntity and INavigation;
• abstract (mustinherit) class EntityConfig;
• infrastructure's classes: AppConfigBuilder and SqlDbContext;
• initial json-files (examples).

Product use:

• install this NugetPackage to application,
• implement model entities by IEntity and INavigation interfaces in application,
• inherit EntityNameConfig class from EntityConfig,
• inherit new context from SqlDbContext if necessary (can be used directly). It is NOT necessary to create instances of entities , they will be created automatically. Attention: instances will be created for all configuration files implementing IEntityConfiguration for ALL project assemblies,
• add a global configurations variable to module Program of the application, i.e.: public IConfigurationRoot AppConfig (for VB - Public AppConfig As IConfigurationRoot),
• add configuration to sub Main of Program: var new AppConfigBuilder appconfigbuilder AppConfig = appconfigbuilder.Build; (for VB - Dim appconfibuilder As New AppConfigBuilder : AppConfig = appconfigbuilder.Build),
• you can set a new file name for settings of an appropriate parameter of the AppConfigBuilder constructor. But this is highly NOT recommended; the filename by default is "appsettings.json",
• define ConnectionString in appsettings.json,
• replace appsettings.json to BaseDirectory of application,
• to initialize a new model you can replace appropriate initial files to /initials. Filenames must match strictly the entitynames, i.e. Category.json for the Category entity,
• use the database, e.g. Using db = new SqlDbContext(AppConfig,"yourconnectionstringname").