Funky. During a build of a web project, Visual Build Pro does some work to try to find where the VS.NET web project (.csproj) is physically located on the drive. This is apparently so it can potentially make changes to the project (increment build versions, properties, etc)

At the bottom of this page shows some of the logic they use to find the project. In our case, our build was hosing up since we had a virtual root defined on the build box that matches the first part of the project listing in the solution (.sln) file.

i.e. "WebApp1" in their example. However, this directory was empty on the drive, per the "clean the sandbox" step. So apparently IIS was pointing VisBuild there, and it would find nothing there.

Fix for the time being was to remove that matching named virtual dir.

Visual Build Professional Help

Found link to this from Chris Sells site, so I guess it's worth a look.

The ADO Guy

A friend of mine actually posted a need for some MS Access work on this site. Never heard if it worked out for him.

Wonder if anything good ever comes out of this site?

Rent A Coder:How Software Gets Done

Actually nGallery, which I've played with at home and is almost there, comes from this site as well.

In addition to the ASP.NET starter kits, these are worth a look.