In general, the more of your code base you have under source control the better. With a VS-based project, your project and solution files are a given. If the application has a database, get the schema (or scripts to generate one) checked in too. Some go so far as to put even the tools required to build the source into source control along with the source itself.
.sln and .csproj files are just text-based, nothing too crazy. My source control (Sourcegear Vault) doesn't like merging them though, so it requires exclusive locks. This may be the key part that have caused issues for your predecessors - just make sure that anything referred to in the .sln and .csproj files also exists in your source tree. Feel free to come back if you have further questions :-) Tom 2008/10/9 DilbertDave <[EMAIL PROTECTED]> > > I think that the introduction of CCnet is going to throw up a few > 'flaky practices' which have only worked in the past because 'so and > so know how to do that!'. > > First step here - standardise project file system structure. > > Thanks for the input > Dave > > On Oct 9, 3:00 pm, "Ross Patterson" <[EMAIL PROTECTED]> wrote: > > On Thu, Oct 9, 2008 at 08:56, DilbertDave <[EMAIL PROTECTED]> > wrote: > > > I think that part of the problem is that we do not check-in > > > the .csproj or .sln files > > > > That sounds like a serious omission. If you don't check them in, you > can't > > build from the source as checked in. > > > > Ross >
