When I build my Setup Project another given project (CustomActions.vsproj) isn't built. It happens that the post build script needs that CustomActions.vsproj's binaries. I could build it manually, but I want to automate this so when another developer download the solution from the repository he won't have to know this trick.
I could automate this by including the CustomActions.vsproj's output in the setup. But I don't want to use this solution because this output shouldn't be included in the MSI.
When I added CustomActions.vsproj's output I could remove it from the Files section and keep it in the build process. This was exactly what I needed.