fluent-interface

Background: We have a project with many modules. We're using EntityFramework 4.2 with FluentAPI (CodeFirst). There is a central project named Diverto.ORM.EntityFramework.SQLServer which contains partial classes that build the context using the FluentAPI (and which has references to every other project on the solution). Recently we received a request from the customer to implement many other features and the solution will need several other projects. Some of these projects will come from another system (Human Resources) and some will be created. The core of the existing solution is a Finance

I am looking for a tutorial on setting up nhibernate. There seems to be few out there, but most are either written in gibberish, or are on an extremely ancient release. Any good resources, possibly even the inclusion of fluent or a code configured install? if you're interested in screencasts, checkout the summer of nhibernate tutorials. They're an execllent way to get up and running Jon Limjap The NHibernate FAQ has everything you need (from blog post 1, that is) including step-by-step discussions on setting up NHibernate. The samples are quite recent, with the blog only starting March 2008.

I'm after some good tips for fluent interfaces in C#. I'm just learning about it myself but keen to hear what others think outside of the articles I am reading. In particular I'm after: when is fluent too much? are there any fluent patterns? what is in C# that makes fluent interfaces more fluent (e.g. extension methods) is a complex fluent interface still a fluent one? refactoring to arrive at a fluent interface or refactoring an existing fluent interface any good examples out there that you have worked with or could recommend? If you could post one tip or thought, or whatever per post. I want

I was wondering what would be the best way to implement a .When condition in a fluent interface using method chaining in a Builder object? For instance how would I implement the .WithSkill() and .When() methods in the following example: var level = 5; var ninja = NinjaBuilder .CreateNinja() .Named("Ninja Boy") .AtLevel(level) .WithShurikens(10) .WithSkill(Skill.HideInShadows) .When(level > 3) .Build() Update - A sample solution can be found here . What I'd do is have NinjaBuilder keep the operations as a list of delegates, rather than applying them, and only apply them when .Build is called.

I am using a fluent interface with inheritance. I declared the base class Constructor protected so you cant create a Foo<Bar> which would result in a ClassCastException on calling add(). But i am having trouble with the static method that returns a new Foo instance. public class Foo<T extends Foo<T>> // if i change to extends Foo i only get warnings { public static Foo<Foo> createFoo() // <-- error { return new Foo<Foo>(); // <-- error } protected Foo() {} public T add() { //... return (T)this; } } public class Bar extends Foo<Bar> { public Bar sub() { //... return this; } } This is mostly an

Hi i'm trying to understand how i could build a readable and also error preventing Fluent-API without to much restriction for the User to hold it simple let's say we want to change the following class to be fluent public class Car { public int Gallons { get; private set; } public int Tons { get; private set; } public int Bhp { get; private set; } public string Make { get; private set; } public string Model { get; private set; } public Car(string make, string model) { Make = make; Model = model; } public void WithHorsePower(int bhp) { Bhp = bhp; return this; } public void WithFuel(int gallons)

Below are two similar fluent API configurations: WithMany() modelBuilder.Entity<Country>() .HasRequired(cou => cou.Currency) .WithMany() .WillCascadeOnDelete(false); WithOptional() modelBuilder.Entity<Country>() .HasRequired(cou => cou.Currency) .WithOptional() .WillCascadeOnDelete(false); What I am trying to express here is: Every Country requires a concrete Currency , but a Currency can be assigned to zero, one or many Countries. Which of the above statements would I have to use? Or in other words: What exactly is the difference between .WithMany() and .WithOptional() operators? If your