what version of vs.net are you using? I'm pretty sure VS2005 and definitely VS2008 there is an option to "show solution file" n solution explorer. and by default i believe it is disabled (unchecked). You may not see the .sln file, but it is there.
Tools > Options > Projects and Solutions > Checkbox: "Always show solution". The only thing that should be allowed to be different on developer machines is the "root" checkout folder. everything below that point must be identical, this way all references are relative paths and they will work just fine across all machines. for example. Developer1 checks out all sourcecode to C:\MyCode\TheApplication Developer2 checks out all sourcecode to e:\Code\RandomTask everything below those folders must be identical. That is how you get reproducible results across all developer machines and the build server. -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] Behalf Of Daniel Sent: Monday, October 13, 2008 11:04 AM To: ccnet-user Subject: [ccnet-user] Re: CC.Net compilation Hi Guys, I don't really understand how that could be otherwise. Our developers are using SourceSafe with VisualStudio and develop code using local copies (check out/in files). SLN file is not part of the project, as it contain paths to files, which can vary from PC to PC (depends on location of local stored copies). .NET doesn't seems to have problem with running our apps without SLN files, is there no way I can get CCNet to compile them so? Thank in advance, Dan On Oct 10, 2:42 pm, Alex <[EMAIL PROTECTED]> wrote: > 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- Hide quoted text - > > - Show quoted text -
