I am supporting a number of .Net developers who are using Subversion to version control their work, but we have been running into a number of issues that seem to revolve around the additional files that Visual Studio uses to manage projects, do debugging, etc. Specifically, it seems that these files are causing conflicts due to the fact that they are already in the repo. I know how to get them out and how to handle them, but I need to know what "they" are first.
So, what are the files/directories that Subversion can ignore, and why can they be ignored?(aka. what do those files do?)
This is a large, rather un-organized ASP.Net site and deploying the site is done via. svn updates, so files needed by IIS to dynamically compile (I think that's what it is) the site as files change needs to be left in the repo.
I have had good luck with this global ignore pattern:
I am running the Resharper plugin, so you can probably ignore that. ".~m2" is for a temporary file my data modeler creates.
Update: Thanks for the up-vote. I've recently added Mac, Dreamweaver, Python, and a few more Visual Studio files that should be ignored.
Something else, if someone accidentally checks in a folder or file that should be ignored, then you will need to manually remove the files from the repository before SVN will start ignoring them again. This is because files that are already in the repo will override any ignore settings.
Old thread, but I want to add that you could use the gitignore example from GitHub, found here, for a good starting point.
I would also not check in the .SDF file. It's large and Visual Studio will recreate it if it is missing. It is a database used for Intellisense as far as I know.
I would probably say anything in the bin directory.
Here's my TortoiseSVN global ignore:
The last 3 help when you transition from Microsoft Visual SourceSafe.