DynamicFluentApis is a .NET (Framework 4.6.1) project written in C# which provides functionalities that allow you to build dynamic assemblies with fluent API support, for types located in other assemblies. Simply put, never, ever write that kind of code again:
using System;
namespace Demo1.LegacyWayOfProvidingFluentApiSupport
{
public class Program
{
public static void Main()
{
var p = new PersonWrapper()
.FirstName("Abdoul")
.LastName("Kaba")
.BirthDate(new DateTime(1990,7,29))
.Object;
Console.Write($"Hello, {p.FirstName}! You say you are {p.Age} ");
Console.WriteLine("and your last name is {p.LastName}, right?");
}
public interface IPerson
{
string FirstName { get; set; }
string LastName { get; set; }
DateTime BirthDate { get; set; }
double Age { get; }
}
public class Person : IPerson
{
public virtual string FirstName { get; set; }
public virtual string LastName { get; set; }
public virtual DateTime BirthDate { get; set; }
public double Age { get => DateTime.Today.Subtract(BirthDate).TotalDays / 365; }
}
public class PersonWrapper
{
IPerson _person;
public PersonWrapper()
{
_person = new Person();
}
public PersonWrapper(IPerson person)
{
_person = person;
}
public string FirstName() => _person.FirstName;
public PersonWrapper FirstName(string value)
{
_person.FirstName = value;
return this;
}
public string LastName() => _person.LastName;
public PersonWrapper LastName(string value)
{
_person.LastName = value;
return this;
}
public DateTime BirthDate() => _person.BirthDate;
public PersonWrapper BirthDate(DateTime value)
{
_person.BirthDate = value;
return this;
}
public IPerson Object { get => _person; }
}
}
}What's the problem with the code above? Well, technically not much! But, for every single type you want to be fluent API capable, you need to manually write a wrapper class like PersonWrapper just to be able to chain method calls. This can be tedious when you have an assembly with dozens or even hundreds of interesting types you want to support.
That's where DynamicFluentApis steps in and generates all that boiler-plate code for you. So, instead of writing code like the one above, you just let DynamicFluentApis generate another dynamic assembly for you that supports fluent API on whatever types you want. You then just grab that assembly and add it as a reference to the latest hot project you're working on.
First things first.
- From your favourite command line or terminal, change the working directory to one of your liking and then pull this repo with git (or download a zipped version):
> git clone https://github.com/bigabdoul/dynamic-fluent-apis.git - Reference both projects, namely
DynamicFluentApisandDynamicFluentApis.Core, within a new console or a unit test project (using .NET Framework 4.6.1). - Add a reference to the console project from the library/libraries or project(s) you want to provide fluent API support with. Let's call these referenced assemblies
HumanResourcesandHumanResources.Web.Mvcfor instance. - Pretending that
HumanResourcescontains thePersonclass, andHumanResources.Web.Mvccontains theBootstrapModalModelclass, write the following code to get started:
using System;
using static System.Console;
using DynamicFluentApis;
using DynamicFluentApis.Core;
using HumanResources;
using HumanResources.Web.Mvc;
namespace Demo2.GeneratingDynamicAssemblies
{
public class Program
{
public static void Main()
{
try
{
// generate a dynamic assembly for the single Person class (very unlikely)
// minimalistic approach:
var result = FluentApiFactory.Configure().Scan(typeof(Person)).Build().ReleaseResources().Result();
WriteAssemblyLocation(result);
// or if you want to scan the whole HumanResources assembly
// you have to be explicit; the ScanAssembly(Assembly) and
// ScanAssemblyFrom(Type) methods retrieve only types marked
// with the custom attribute FluentApiTargetAttribute
var types = typeof(Person).Assembly.GetTypes();
result = FluentApiFactory.Configure(overwrite: true).Scan(types).Build().ReleaseResources().Result();
WriteAssemblyLocation(result);
// you can even generate multiple dynamic assemblies
// with this full-blown approach:
using (var config = FluentApiFactory.Configure(true))
{
FluentApiFactoryExecutionResult result1 = null;
result = config
.OnError(error => WriteLine($"A critical error occured: {error}"))
.OnDeleteError((error, builder, file) =>
WriteLine($"Could not delete the file '{file}'. Reason for failure: {error.Message}")
)
.WithOverwriteOptions()
// these 'Set...' methods modify the default prefix and suffix values
// public interface IPerson {...}
// internal sealed class PersonCloned : IPerson {...}
.SetProxyClassNameSuffix("Cloned")
.SetFluentTypeNamePrefix("Magic")
// public class MagicPerson { ... public virtual IPerson Target { get; } }
.SetWrappedObjectPropertyName("Target")
.WithConfig()
.ScanAssemblyFrom(typeof(Person))
.Build()
.SetResult(r => result1 = r)
.Reset()
// default options use 'Proxy' suffix (the above would have been
// 'PersonProxy' instead of 'PersonCloned'),
// and 'Fluent' prefix ('FluentPerson' instead of 'MagicPerson')
.WithDefaultOptions(overwrite: true)
.ScanAssemblyFrom(typeof(BootstrapModalModel))
// will generate, amongst others, the following types:
// public interface IBootstrapModalModel {...}
// internal sealed class BootstrapModalModelProxy : IBootstrapModalModel {...}
// public class FluentBootstrapModalModel {...}
.Build()
.Result();
WriteAssemblyLocation(result);
WriteAssemblyLocation(result1);
}
if (result.Succeeded)
{
WriteLine("What's next? Grab that file and a reference to it in your project.");
WriteLine("You'll be able to use your fluent wrapper as shown in the next demo.");
Write("The assemblies' names are similar to: HumanResources.DynamicFluentApis.abcdef.dll ");
WriteLine("and HumanResources.Web.Mvc.DynamicFluentApis.fedcba.dll");
Write("Where 'abcdef' and 'fedcba' are (for instance) the hash codes generated ");
WriteLine("for the dynamic fluent API assemblies.");
}
}
catch(Exception ex)
{
WriteLine($"An unexpected error occured: {ex.Message}");
}
void WriteAssemblyLocation(FluentApiFactoryExecutionResult result)
{
if (true == result?.Succeeded)
{
WriteLine($"The generated assembly is {Environment.CurrentDirectory}\\{result.AssemblyFileName}!");
}
else
{
WriteLine("Could not create the assembly!");
}
}
}
}
}You get the idea? Perfect! Now, before we proceed to see how we can use the assemblies generated in the previous demo, let's examine what's going on here.
using System;
using DynamicFluentApis.Core;
using HumanResources.DynamicFluentApis;
using HumanResources.Web.Mvc.DynamicFluentApis;
using static System.Console;
namespace Demo3.ShowcasingFluentApiSupport
{
public class Program
{
public static void Main()
{
// fluent API support demo coming soon...
}
}
}