Correct way of integrating SVN source control and Visual Studio .NET 2005/2008?

Question

What is the best-practice for maintaining a source code repository that automatically (or, at least, by default) rejects the inclusion of /bin, /obj, *.suo, etc. files?

Should each developer be required to set a "global ignore" pattern list for their SVN client installation? [This seems too broad of an exclusion.]

Or, should the source repository maintainer flag each offending file and directory with an SVN:exclude? [This seems too time consuming.]

Or, is there another way to do this? Is it possible with SVN to create ignore lists that are folder-level specific?

Answer 1

Set the svn:ignore property on directories that contain files/directories you want to ignore. It's a one-shot deal.

Answer 2

We currently use a mandated global ignore pattern on the client side, which is less than ideal as you've pointed out. We do at least have a document for setting up and configuring the development environment, which includes the latest authoritative ignore pattern (such as this one Best general SVN Ignore Pattern?).

I'm curious about the behavior of svn:ignore as Romain Verdier suggested. I've posted a comment to his answer.