This latest post on developing a fluent interface for the Oslo System.Identity schema will start an implementation of the Party class. Per the architectural specifications for the fluent interface, the Party class will adhere to the Law of Demeter and “ Tell, Don’t Ask ” . As the Party class is large...

<Author’s Note> It’s been quite a while since my last blog post. The reason for the gap was due to my non-work time being consumed with swimming (some might say wallowing ;-) in the architectural soup writing a ThinkWeek paper related to Microsoft IT (MSIT) software architecture. Writing the...

As I wrote about last time , leveraging the System.Identity schema with the Oslo Repository introduces some ORM database persistence considerations into the design of the fluent interface . In the last article I introduced how to override the Equals() method inherited from System.Object . In accordance...

As I wrote in Part 2 of the series, System.Identity ships in the latest Oslo CTP as part of the Oslo Repository . This has the direct effect of introducing ORM database persistence considerations into the design of the System.Identity fluent interface I’ve been crafting . One of these considerations...

Part 1 of this series functioned as an introduction to the motivations for creating a fluent interface for Oslo’s System.Identity . Part 1 also covered a number of architectural and design specifications that will be followed in the shaping of the interface’s code. In this post I’ll continue the crafting...

<Author’s Note> A very talented Developer I know just recently gave me some very succinct feedback on my blog - “good blog…too long”. As I respect this Developer’s opinion quite highly (not to mention I always try to listen to Developers ), I am going to start putting his suggestion into...