Recommended files to store in vault for VS.NET (C#)

brettski · Post by **brettski** » Mon Nov 15, 2004 10:33 pm

I am new to source control and VS.NET. I have used CVS in the past with other languages but have been looking for newer Source Control programs. I ran into some posts from Eric Sink on the Web and found my way here and I am very interested in using this product in our shop. I have been using the single user mode for a little while now and have gone back and forth between using the IDE and GUI and I like the abilities much better of the GUI (specially since I come from the CVS world).

I am looking for which files/directories should be included in the repository for a multi-user environment. I figure that obj and bin directories shouldn't be included. Could you please tell me what the best practices for what to store using VS.NET and C#.

Thanks in advance.

Brett

Post by **jclausius** » Tue Nov 16, 2004 8:23 am

Brett:

Any file in your project / solution which can be modified by your use or through the use of an IDE. These files include ( but are not limited to ):

.cs
.resx
.csproj
.sln
.asax
.aspx
.asmx
.asax.cs
.aspx.cs
.asmx.cs

Note, some people prefer to have VS.Net control this situation. In this case, if you enable the IDE client for use within VS.Net, and then add a project or solution to Source Code Control, Visual Studio will create the appropriate folders within a Vault repository and then add the project / solution files to the repository.

If you have some specific questions, please post back.

brettski · Post by **brettski** » Tue Nov 16, 2004 8:53 am

Thank you for the information. How about sln and suo files which are more user specific not app specific?

Post by **jclausius** » Tue Nov 16, 2004 9:06 am

I believe .suo files should not be included. As for .sln, its your call.

if everyone on the team uses the same solution, then it is a time saver to have the .sln(s) there.

For example, we have a Vault client / server / admin tool solutions, used by each individual team. These are all present in Vault, so someone coming into a team can grab the particluar Vault solution, and automatically be up and running w/ all of the necessary projects which make up the solution.

superkinhluan · Post by **superkinhluan** » Sun Nov 21, 2004 11:20 pm

I also have one question regarding this topic. In my projects, I often have images and/or other binary files. Should I include those into repositories as well ? Vault stores all files in database, so is it good to store large binary files, which may cause performance hits through web service calls.

Thanks.

Post by **jclausius** » Mon Nov 22, 2004 8:56 am

Vault is efficient at storing both types. There is no performance difference between either a binary file or text file.

Now, if a file is large, 100+ MB, then there might be a small wait in calculating the difference on a commit for a version change, but I don't think it would be too noticeable given today's hardware.

In sum, the variables for binary based files would be how big the initial file is, and how large are the changes on version changes.