http://blogs.msdn.com/b/nblumhardt/archive/2008/12/29/explicit-context-dependencies.aspxAs a follow up from my last post about Global Container vs. Injected Context , I would like to share this snippet from Component Software , which casts the difference between the two approaches in another light: &quot;A software component is a unit ofen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/nblumhardt/archive/2008/12/29/explicit-context-dependencies.aspx#9256423Tue, 30 Dec 2008 03:52:15 GMT91d46819-8472-40ad-a661-2c78acb4018c:9256423Bryan Watts<p>Calling upon a static implementation, such as a Global Container, is the highest form of coupling - there is no room for abstraction. The context of an entire app domain is assumed, which precludes more-specific contexts.</p> <p>Components, by definition, cannot assume any context, so they cannot rely upon static implementations.</p> <p>This principle can help ensure functionality is properly bounded. Thanks for the tip on the book!</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=9256423" width="1" height="1">