June, 2009

In TFS 2008 we made quite a few improvements to build, such as scheduled builds and continuous integration. The continuous integration feature is nice for detecting failures in the build as soon as possible to ensure minimal downtime and reduce the chance of generating a bad nightly build. However, it’s not a perfect solution since even when the build fails it is possible for others to submit unrelated changes and keep the build broken. As a first measure to aid this scenario, Buck Hodges wrote a...

Download migration documents from - http://www.microsoft.com/downloads/details.aspx?FamilyID=bd94c260-b5e0-4d12-93ec-53567505e685&displaylang=en · WF Migration Overview - Overview of the document collection and an initial starting place for the WF3 developer · WF Migration: Best Practices for WF3 Development - How to design WF3 artifacts so they are more easily migratable to WF4 · WF Guidance: Rules - Discussion of how to bring rules-related investments forward into .NET 4 · WF Guidance: State...