alkampfer on November 29th, 2011

In an old post I dealt with a possible implementation of a BaseEntity class that stores all properties in a State object (based on a dictionary to store properties). Technically speaking, this solution have no drawbacks respect using field variables to store properties values, but it can give a lot of benefit. If you see [...]

kick it on DotNetKicks.com

Continue reading about Using a state object to store object property values.

alkampfer on October 27th, 2011

After lots of year working with NHibernate I started to think that probably the whole concept of ORM can be considered an Antipattern. Some people prefer a “classic” approach to the problem, data is the key concept and most of the logic is inside a storage based on Relational Model. Is this wrong? Absolutely not, [...]

kick it on DotNetKicks.com

Continue reading about Square peg in a round Hole

alkampfer on August 12th, 2011

I’ve stumbled upon this funny comic   I usually use long Random generated password, that I store in KeePass for all services that I really care about, (home banking, amazon account that has my credit card, etc), and tend to use easy to remember password for services I do not care very much (stupid online [...]

kick it on DotNetKicks.com

Continue reading about Is there a reason to put restriction on password?

alkampfer on May 11th, 2011

Scenario: I have some service that runs in the background, but I want the user to be able to launch interactively with a  windows form application and I want to intercept all log4net messages issued by the various components that works in the background. Thanks to the supereasy way to write an appender in log4net, [...]

kick it on DotNetKicks.com

Continue reading about Intercept Log4Net message in a Windows application

alkampfer on May 6th, 2011

Some days ago I blogged about an implementation of persistent cache component based on Managed Esent and PersistentDictionary. This component is injected into other components thanks to Inversion of Control and it is a Singleton object. Being a singleton is a requisite because it permits to different dependent objects to share the same cache, moreover [...]

kick it on DotNetKicks.com

Continue reading about Lifecycle of singleton objects