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 bui

Answer 1

Put the following files in version control:

• .dsw (VS6 workspace)
• .dsp (VS6 project)
• .sln (VS Solution)
• .*proj (VS Project files of various types)
• of course your source files and other artifacts you create

Do not put the following files into version control:

• .ncb (something to do with browsing or intellsense)
• .suo (user workspace settings like window placement, etc - I think)
• .user (user project settings like breakpoints, etc - I think)

Also, don't put in any object files, executables, auto-generated files (like headers that might be generated).

As for executables and other generated files - there might be an exception if you want to be able to archive releases. That might be a good idea, but you'll probably want to manage that a little differently and possibly in a different place than your source code. If you do this, also archive your .pdb files so you can debug the stuff later. you might want to use a Symbol Server to store you archived symbols (see Debugging Tools for Windows for the symbol server and its documentation).

Here's my list of VS-specific files that I exclude from SVN:

Ankh.Load
*.projdata
*.pdb
*.positions
*proj.user
*proj.*.user
*.ncb
*.suo
*.plg
*.opt
*.ilk
*.pch
*.idb
*.clw
*.aps