Coding and Dismantling Stuff

Don't thank me, it's what I do.

About the author

Russell is a .Net developer based in Lancashire in the UK.  His day job is as a C# developer for the UK's largest online white-goods retailer, DRL Limited.

His weekend job entails alternately demolishing and constructing various bits of his home, much to the distress of his fiance Kelly, 3-year-old daughter Amelie, and menagerie of pets.


  1. Fix dodgy keywords Google is scraping from my blog
  2. Complete migration of NHaml from Google Code to GitHub
  3. ReTelnet Mock Telnet Server à la Jetty
  4. Learn to use Git
  5. Complete beta release FHEMDotNet
  6. Publish FHEMDotNet on Google Code
  7. Learn NancyFX library
  8. Pull RussPAll/NHaml into NHaml/NHaml
  9. Open Source Blackberry Twitter app
  10. Other stuff

NHibernate Error "Object references an unsaved transient instance" - Fixed!

Hi all,

Just a quick post to share some learnings I've had around a good ol' NHibernate "Object references an unsaved transient instance" error message. In essence, this message is telling you that you're trying to save an object which has a reference to another unsaved object, and NHibernate for one reason or another is unable to work out which object to save first so that it can work out the ID to apply to the other end of the reference. What went wrong and how did I fix it?


Categories: Sneaky Bug Fixes
Permalink | Comments (0)

Spring.Net - Unable to locate Spring NamespaceHandler for XML schema namespace

Hi all,

I'm just putting this out in the wild because I've just spent a good few hours banging my head against a wall!  If you're using for dependency injection, and you're getting an error similar to the following:

"Unable to locate Spring NamespaceHandler for XML schema namespace []"

Note the empty brackets - make sure you've got a correct namespace on your Spring.Net configuration!  Just to recap, your web.config / app.config should have the following custom configuration section, specifically including the bit in bold.  This namespace appears to be hardcoded into the Spring.Core assembly source as a trigger for "good" behaviour:


      <resource uri="config://spring/objects" />
    <objects xmlns="">


Take care all,


Categories: Sneaky Bug Fixes
Permalink | Comments (0)