I woul further add to Daniel's point that if each solution is individually modified for each developers machine, then this is way outside of sotware engineering norms, and it should be rectified. Yoru solution should build on all machines in all cases. This is the whole point behind continuous integration and CruiseCOntrol.NET to a certain extent. I would be very interested in hearing a good reason for independant solutions. How, after all, would any single developer have any idea of how their compile is doing when it has no relation to any other compile. You could not possibly debug under that situation as you may be debugging something completely different from what your customers are using.
On Oct 10, 5:49 am, Daniel Hommel <[EMAIL PROTECTED]> wrote: > Daniel swrites: > > > Hi Guys, > > > thanks for that, that make sense. > > > I looked up that tasks thing, and found the paragraph of using MSBuild > > - just one thing - our project, stored in VSS doesn't contain .sln > > file (which seems to be required). I understand .sln file is specific > > to each developer's machine. > > > Any ideas? > > > Thanks, > > Dan > > As far as i know the user or machine specific options are not stored in > the solution file. The solution is just the "top-level project". > > But even if you don't want to check in the solution you should still be > able to use MSBuild to build the projects (.csproj files or similar). A > drawback is that you need to run MSBuild on all the projects in the > correct order. > > I hope this helps. > > regards, > > Daniel
