Hi that depends if you're developing that LIB and EXE project yourself, you can set up a project reference between them, so Visual Studio knows the build order.
When you compile the solution, (not the individual projects), Visual Studio/MSbuild/Nant scans the projects for project references, and build them in the correct order. with kind regards Ruben Willems On Fri, Oct 10, 2008 at 4:31 PM, Derek Hofmann <[EMAIL PROTECTED]>wrote: > Take the case of a solution containing two projects, LIB and EXE. Project > EXE links in the results of project LIB but the solution doesn't have this > dependency setup. In this solution, "build solution" will often build LIB > first then EXE just by chance, but someone who makes a change to LIB and > then does "build project" on EXE won't see LIB get rebuilt automatically > like it should. > > I think doing "build project" on each project within the solution, cleaning > after each one, will detect this kind of problem with the solution file. > > On Thu, Oct 9, 2008 at 11:34 PM, Ruben Willems <[EMAIL PROTECTED]>wrote: > >> 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 >> > >
