Effective Thoughts

Recently creating a TFS 2008 build for VS.Net 2005 projects, I kept receiving the following: ...error MSB4019: The imported project "C:\Program Files\MSBuild\Microsoft\VisualStudio\v8.0\WebApplications\Microsoft.WebApplication.targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk. I discovered the v8.0 hive didn't even exist on the file system. At first, I thought I was missing something like the .Net 2.0 SDK. Unfortunately, installing that didn't add the files to v8.0. Eventually, I simply copied the v8.0 hive off a VS.Net 2005 developer machine and onto the build server. Maybe not the prettiest but it solved my build problem.

Session Details: Did you know that .csproj and .vbproj files are really MSBuild files? More than build processes though, MSBuild is a full-featured automation language. It includes structured control flow, variables, refactorability, error handling, logging, and powerful extensibility. You can easily integrate MSBuild into your own enterprise processes and start adding value right away. We'll also look at how Team Foundation Build extends on MSBuild and adds robust integration with Team Foundation Server. Speakers Bio: Steve Andrews is a Team System MVP, and has been working as a developer for more than 9 years. During this time, he has designed and developed applications in such widely varying areas as trust accounting, medical information management, supply chain management, and retail systems. He is currently employed at RDA Corporation in Philadelphia, PA, as a Software Engineer and a team member in their Architectural Guidance evangelism team. Steve is also an MCP, ICSOO, Spe...