http://blogs.msdn.com/b/stmteam/archive/2010/05/12/stm-net-devlab-incubation-complete.aspxI would like to thank everyone who downloaded and participated in the MSDN DevLab and tried our .NET 4.0 Framework enabled to use Software Transactional Memory (STM.NET). Now that we have shipped VS2010, we decided to conclude that DevLab. We appreciateen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/stmteam/archive/2010/05/12/stm-net-devlab-incubation-complete.aspx#10051407Wed, 18 Aug 2010 11:21:02 GMT91d46819-8472-40ad-a661-2c78acb4018c:10051407Anton<p>link to STM Programmer&#39;s Guide does not work &nbsp;</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=10051407" width="1" height="1">http://blogs.msdn.com/b/stmteam/archive/2010/05/12/stm-net-devlab-incubation-complete.aspx#10012262Thu, 13 May 2010 04:43:03 GMT91d46819-8472-40ad-a661-2c78acb4018c:10012262JudahGabriel<p>Wow. So STM.NET is retired. Was technical problems the final blow? I remember Joe Duffy describing a &lt;a href=&quot;<a rel="nofollow" target="_new" href="http://www.bluebytesoftware.com/blog/2010/01/03/ABriefRetrospectiveOnTransactionalMemory.aspx&quot;&gt;fundamental">http://www.bluebytesoftware.com/blog/2010/01/03/ABriefRetrospectiveOnTransactionalMemory.aspx&quot;&gt;fundamental</a> technical problem discovered in the STM bits&lt;/a&gt; - is that what put the nail in the coffin?</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=10012262" width="1" height="1">