Use NMock to eliminate dependencies during the development cycle and improve code qualityhttp://blogs.msdn.com/peterlau/archive/2006/06/15/632372.aspxDuring the development cycle, the scenario often occurs where Developer A is working on a component that depends on a component worked on by Developer B. Of course, B’s component isn’t ready yet. ‘A’ feels hopelessly stuck and ends up twiddling her thumbsen-USCommunityServer 2.1 SP1 (Build: 61025.2)Moments of Enlightenmenthttp://blogs.msdn.com/peterlau/archive/2006/06/15/632372.aspx#632378Thu, 15 Jun 2006 18:48:33 GMT91d46819-8472-40ad-a661-2c78acb4018c:632378JrzyShr Dev GuyAs this blog evolves, I’ve been debating what type of blog it should be.&amp;amp;nbsp; One of my primary goals...re: Use NMock to eliminate dependencies during the development cycle and improve code qualityhttp://blogs.msdn.com/peterlau/archive/2006/06/15/632372.aspx#632607Thu, 15 Jun 2006 21:43:45 GMT91d46819-8472-40ad-a661-2c78acb4018c:632607Bill PiercePeter, <br>You might also want to checkout RhinoMocks (<a rel="nofollow" target="_new" href="http://www.ayende.com/projects/rhino-mocks.aspx">http://www.ayende.com/projects/rhino-mocks.aspx</a>). &nbsp;Oren put together a great package that has additional features over nMock. &nbsp;RhinoMocks is easier to work with as well (my opinion only :). <br> <br>-Billre: Use NMock to eliminate dependencies during the development cycle and improve code qualityhttp://blogs.msdn.com/peterlau/archive/2006/06/15/632372.aspx#637068Mon, 19 Jun 2006 20:27:27 GMT91d46819-8472-40ad-a661-2c78acb4018c:637068peterlauBill, <br> <br>Thanks for the info on Rhino-Mock. &nbsp;I checked it out over the weekend and it looks pretty slick! &nbsp; <br>-Peter (aka JrzyShr Dev Guy)