<p>I have been using <a href="http://en.wikipedia.org/wiki/Inversion_of_control" rel="nofollow noreferrer">IoC</a> for a little while now and I am curious if I should use Microsoft's <a href="http://msdn.microsoft.com/en-us/library/dd203101.aspx" rel="nofollow noreferrer">Unity</a> framework (official name "Unity Application Block").  Does anyone have experience using it?  So for I have been copying my IoC container code from project to project, but I think it would be better to using something standard.  I think IoC can make a HUGE difference in keeping component based applications loosely coupled and therefore changeable but I am by no means an expert on IoC, so I am nervous to switch to a framework that will just paint me into a corner as a dependency I will one day want to walk away from.</p>

I've played with CompositeWPF (aka Prism) - successor of Composite app block. From my experience Unity works much better as compared with previous version of ObjectBuilder. However it's up to you to evaluate IoC frameworks and choose one suited for your needs.
Unity tutorials & samples
Unity IoC Screencast