Hi
why would you want to do it this way?
This is my solution for the same problem you're facing (I think) :
° in my company all the devs work at the D or E drive,
the C drive is the system disk, and may only be used by the system
° the build server is a virtual server, so they made an exception for this
rule,
and it pulls down the source to the C drive.
Should this exception not be the case, I would have made pull the source
to D:\BlaBLa\somestupidFolder\... or something that would never exist on
a dev PC
° clean all the projects in the solution, I just delete all the bin and obj
folders
from the source folder downwards. I do not use the clean task of VS
(takes to long)
° Build the solution
If there is somewhere a hardcoded reference to let's say
e:\myproject\lib\some.dll, it will show up
with kind regards
Ruben Willems
On Fri, Oct 10, 2008 at 3:26 AM, DHofmann <[EMAIL PROTECTED]> wrote:
>
> Is there a way to, one at a time, build and then clean each project
> (and dependencies) within a Visual Studio solution individually
> without some kind of manual intervention like creating separate tasks
> for each project? The purpose would be to check that the dependencies
> are setup correctly.
>
