asp.net mvc - What direction should we go for maintaining a document management system? -

We created an application on top of ASP.NET MVC, now let us allow our users to manage their documents online. As part of this system requirement, users want to upload and share documents with other members of their organization.

We have an existing web application which is needed as a value add-on. We are trying to figure out what our requirements are in this requirement. We are finally looking for a back and solution that will help us with lots of work related to version control.

We need to upload documents ...

• Upload the document
• View the version history of each document

• Calculate the file size

We are considering:

Creating your domain model and in the database Storing documents

Integrate with dissecting to use it as our back end.

Which approach has worked for you? What are some benefits and drawbacks for each? Are there any other options?

The solution we choose needs to follow the following criteria:

• We need to fit well into our automated deployment.
• We want some light weight, and it's easy to upgrade and deploy

Subversion sound like the best bet here, just train users who need to manage documents to use and then storing your document is a subdirectory of your project. .