Ok, this is causing me problems again. I can't have developers share solution file in the SourceSafe project, because then it's cannot be modified by neither of them, and if it was, I accounter issues.
On the other hand i need this file for compilation. I don't get this - why somehow .NET application can be propertly compiled by IIS on the server, yet it can't run builds without solution files? On Oct 14, 1:11 pm, Alex <[EMAIL PROTECTED]> wrote: > That is correct you need to install MSBuild 3.5 to compile VS 2008 > code. It comes with the .NET framework. > > On Oct 14, 7:08 am, Daniel <[EMAIL PROTECTED]> wrote: > > > > > Ok, i managed to include solution file, however it seems like MSBuild > > from .NET 2 can't compile VS2008 code (i'm getting error message that > > v7 though 9 are supported only). > > > Dan > > > On Oct 13, 4:20 pm, "Phil Sayers" <[EMAIL PROTECTED]> wrote: > > > > oh yeah...and... > > > > those local stored copies...require by policy they be in the exact same > > > location. or .. put them in source control too, and make the > > > projects/solutions reference them using relative paths. > > > > -----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 -- Hide quoted text - > > > > - Show quoted text -- Hide quoted text - > > > - Show quoted text -- Hide quoted text - > > - Show quoted text -
