title: Best practices for Subversion and Visual Studio projects
body: <p>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.</p>