Is it feasible to use svn for documents

Question

We need to have documents shared between clients (CRM-like functionality). Users need to be able to:

• Edit the documents and save them again
• Attach new documents

Our application is coded in WPF with WCF for data-transport and NHibernate/SQL for data on the server.

what we're thinking is to use SVN and have the app create a local check-out of parts of the repository (when they click a document, it is checked out by SVN in the background and opened from the local path) - When saved it will silently (using monitoring of the path) be committed back to the repository.

Question: Is this feasible - or are there better solutions to this?

EDIT 1: Summary so far:

• I'll look into using Git/Mercurial instead of SVN
• Document size (revisions) might be prohibitive pending tests
• SharePoint is an option (although not viable in my case as the cost alone is prohibitive) - I will look into the alternatives for SharePoint, tho.
• Not much experience out there about using repositories for many users although it works for small teams..
• Wiki software might be an alternative to SVN.

Thanks for all the feedback - I'll keep it open a bit longer.

EDIT 2: Summary after a few days of work - I have a client working - see my progress here.

Answer 1

Based on the heavy .NET references, are you all set up with MSDN? Perhaps you can make use of SharePoint...which may already be included within your MSDN account.

Answer 2

You might also want to consider using a Wiki for document management - I've seen this done and do it myself for my own organisation. We're using Atlassian's Confluence Wiki. Confluence provides for the versioning and general management of documents.