In the first article in this three-part series, I show how to write project files for MSBuild. In the second article I detail how to write, debug, and install your own custom tasks that can be used to enhance your MSBuild project files. In this article, you first see how MSBuild supports Visual Studio solution files. Then I show how to be notified of build events in order to write your own custom logging mechanism. Some details will change in the future, as will be apparent if you install the Visual Studio 2005 Community Technology Preview available for VSLive attendees and MSDN subscribers. Throughout this article, a special "Technology Preview" framing will highlight the differences between the Whidbey PDC bits and the preview version of Visual Studio 2005. In the accompanying sample projects contained in MSBuildSamples3of3.msi, files with the suffix "-v2" are compliant with the Community Technology Preview and a TechPreview folder stores the C# implementation of the different loggers which are compliant with the Preview bits. You should take a look at the first article of this series to learn the changes in the XML project file syntax.