sfeldman.NET

Development, QA, Deployment, Production Support, Infrastructure,… it doesn’t matter what aspect of software you are affiliated with. Automation is your best friend. And if it is not, you are living a worse nightmare without yet realizing it.

Looks like more people are looking into OODB. This post I found recently is experimenting with db4o, as well as has a healthy discussion in the comments section. This is ties into what I felt and thought a while ago after reading a book on db4o.

If you are into trance music, check armadamusic out.

This is a good joke. As always, in every joke, there’s a lot of truth.

The question came from my son… and he was right. There’s something wrong with it.

As a part of the build script I tend to generate AssemblyInfo.cs in order to inject assembly information dynamically, such as version, name, etc. One gotcha I ran into lately, is when you have internals that are testable and need to generate that information from NAnt as well.

Each time we use NHibernate, we have to share production and semi-production code for NHibernate SessionFactory. Production code is the portion that is actually responsible to generate the SessionFactory on startup. Semi-production code, is the code that generates SessionFactory for purpose of schema extraction (SQL statements we use to generate DB). This time around, the smell had to be removed. Having identical code duplicated not only risky, but also becomes intolerable once it grows beyond a single line. This is our new SessionBuilder, that leverages the same code to generate SessionFactory for run-time purpose and schema generation at “design” time.