Hi, I had the same problem, and the problem was about the build output
configuration ("Any CPU", etc) which was different from the web site
avaliable configurations (check on the web project) and the class libraries,
so I had to use two different build types for this, one with the valid
configuration for the class libraries, and one for the web site.
Maybe other approach to solve this, is using a custom task build, these are
just builds you can program, and add to the build project to execute at the
point you want (before/after running test, before/after deploy, etc) you can
find information about this on the Visual Studio 2005 SDKs
--
Luis Fraile
MCSD.NET
[quoted text, click to view] "Ian" wrote:
> Hello all,
>
> This isn't so much of a *problem* as it is that I know what I want to
> do, but I'm not sure where to start. We have a Team Foundation Server
> (TFS) install and a Team Build, which we've used Scheduled Tasks to
> execute nightly at midnight. The solution contains several class
> libraries, but ultimately the deliverable is a web site.
>
> When the team build completes, it copies the "output" of the build to
> the locations specified in the DropLocation, however this appears to
> only contain the generated assemblies from the class library projects
> and none of the web-related output. (i.e. no assemblies related to the
> web project, none of the static files *.css/gif/etc, and certainly none
> of the .aspx files)
>
> We're looking for a way to have a nightly build, that, if successful,
> deploys the completed web site to an internal staging server. What
> should I be looking for in terms of achieving this? I've read some
> bits here and there about Web Deployment Projects, but it seems like
> this is something that happens outside the scope of the team build
> process.
>
> Thanks for any advice,
> Ian
>
