grinderofl / fluentmodelbuilder

Convention based automated Model Builder for Entity Framework Core

FluentModelBuilder

Conventional, automated, and fluent way to configure the backing model of your DbContext.

• Class-based configuration
• Expression-based configuration
• Assembly-based discovery
• Alterations
• Entity Type Sources
• Conventions
• Entity Type Overrides
• Dependency injection support

All this while keeping in mind developers coming from background of Fluent NHibernate, which this project is greatly inspired by.

Getting started

• Read the Introduction
• Get latest binaries from NuGet

NuGet:

• https://www.nuget.org/packages/FluentModelBuilder/

Build status

fluentmodelbuilder's Issues

Allow invalidating model depending on criteria

Add a custom ModelCacheKeyFactory which takes an ModelInvalidator as an argument, and creates a new type of ModelCacheKey that contains "version" property. This property is then increased if Model is invalidated.

Upgrade to use IModelCustomizer

As per update to EF, instead of adding a Model Convention, replace IModelCustomizer.

Compatible with EntityFramework Core 2.0 ?

I got the following exception when attempting to migrate an existing project to .Net Core 2.0 assemblies:

- $exception {System.TypeLoadException: Method 'ApplyServices' in type 'FluentModelBuilder.Configuration.FluentModelBuilderOptionsExtension' from assembly 'FluentModelBuilder, Version=1.4.1.1411, Culture=neutral, PublicKeyToken=null' does not have an implementation. at FluentModelBuilder.Extensions.DbContextOptionsBuilderExtensions.Configure(DbContextOptionsBuilder optionsBuilder, AutoModelBuilder[] builders)

If FluentModelBuilder compatible with .Net Core 2.0?

Create IEntityTypeOverride and IModelBuilderOverride using service provider

Add a factory for instantiating objects and call via ModelCustomizer (maybe in context?) when creating override instances.

Experiment with late-creating of alterations.

Model Caching

Hi,
is there a way to avoid caching of model with FluentModelBuilder?
I have a database with multiple tables, all with the same structure. each table naem has a different prefix.
CREATE TABLE X000001Log([Id] [int] NOT NULL, [Date] [datetime] NOT NULL)
CREATE TABLE X000002Log([Id] [int] NOT NULL, [Date] [datetime] NOT NULL)
CREATE TABLE X000003Log([Id] [int] NOT NULL, [Date] [datetime] NOT NULL)

In an ASP .NET 5 application the model is cached the first time it has been built.
The OnModelCreating is fired only once time for the entire life cicle of the app

        private string _prefix;
        private bool _rebuildModel;

        public MyContext(string prefix, bool rebuildModel) {

            _prefix = prefix;
            _rebuildModel = rebuildModel;
        }

        protected override void OnConfiguring(DbContextOptionsBuilder options)
        {
            options.UseSqlServer(@"Server=(local);Database=mydb;Trusted_Connection=True;");

            if (_rebuildModel)  {
                 /* what can i do here? */
            }
        }
        protected override void OnModelCreating(ModelBuilder modelBuilder)
        {
            modelBuilder.Entity<LOG>().ToTable(string.Concat(_prefix, "log"));

Any suggestion?
Thanks in advance

Refactor tests and ensure they cover all API paths

• Currently not all API paths are covered by tests.
• All tests should be restructured to be more coherent with AAA pattern (like BuildingUsingServiceProvider)

ToTable does not exist

In the introduction documentation:
https://github.com/Grinderofl/FluentModelBuilder/wiki/0.-Introduction

You have a statement that reads as:
mapping.ToTable("MyEntities");

But ToTable is not an available method on the mapping object. How can this functionality be achieved? (Using code first)

Replace explicit UseModel with IModelSource implementation

This way, model can be created when first requested, giving the capability for dependency injection.

Caution needs to be taken with database prociders which have their own ModelSources.

Maybe inherit from those providers and override the modelsource there?

Synchronise actual API with doc api

AddEntityAssemblies()
Using(AutoModelBuilder otherBuilder)
UseOverridesFromAssembly(Assembly assembly)

Add more extensions for EntityDiscoveryOptions

Needs methods like discover.When(x => x.Namespace.EndsWith(".Domain")) to allow more expressive syntax.

Implement in #2

Enable single ConventionSet item alteration

Add supporting interfaces like IEntityTypeConventionOverride, which expose an Alter(IList<IEntityTypeConvention>); method

Additionally, add an AddAlterationsFromAssembly() method to ConventionSetAlterationCollection which scans an assembly for all of those types of convention overrides.

Make Scope property accessor

class ScopeBuilder
{
private AutoModelBuilder _amb; // ctor
    public AutoModelBuilder Early()
{
    _amb.SetScope(Early);
    return amb;
}
}

Consider having assembly scanning as a separate convention

Currently, assembly scanning is a core mechanic in a few conventions, requiring specifying assemblies in both conventions separately. Consider moving assembly scanning into its own convention, and allow other conventions to call that instead.

Possible proposals:

FluentModelBuilderOptions => ModelBuilderConventionSource property

opts.UseAssemblies(x => x.Containing<Type>());
opts.AddEntities(x => x.WithBaseType<Entity>());
opts.AddOverrides();

Allow alterations to add alterations

Maybe in the form of queue?