Best practices for Subversion and Visual Studio projects

Question

I've recently started working on various C# projects in Visual Studio as part of a plan for a large scale system that will be used to replace our current system that's built from a cobbling-together of various programs and scripts written in C and Perl. The projects I'm now working on have reached critical mass for being committed to subversion. I was wondering what should and should not be committed to the repository for Visual Studio projects. I know that it's going to generate various files that are just build-artifacts and don't really need to be committed, and I was wondering if anybody had any advice for properly using SVN with Visual Studio. At the moment, I'm using an SVN 1.6 server with Visual Studio 2010 beta. Any advice, opinions are welcome.

Answer 1

According to MSDN:

You can add the following files to Visual Studio source control:

• Solution files (*.sln).
• Project files, for example, *.csproj, *.vbproj files.
• Application configuration files, based on XML, used to control run-time behavior of a Visual Studio project.

Files that you cannot add to source control include the following:

• Solution user option files (*.suo).
• Project user option files, for example, *.csproj.user, *.vbproj.user files.
• Web information files, for example, *.csproj.webinfo, *.vbproj.webinfo, that control the virtual root location of a Web project.
• Build output files, for example, *.dll and *.exe files.