4

does anyone know about a document management system (or modules) that can be integrated with .NET?

Thanks.

AnthonyWJones
  • 187,081
  • 35
  • 232
  • 306
lmsasu
  • 7,459
  • 18
  • 79
  • 113
  • 7
    Is it possible to use Sharepoint? That would provide a lot of functionality with little coding on your part, though you'd have to do configuration. – DOK May 03 '09 at 19:12
  • @DOK: sounds like an answer to me, any reason you haven't posted it as answer? – AnthonyWJones May 03 '09 at 19:15

5 Answers5

4

Here is a list of some of the most common DMS found in enterprises nowadays. (they all could be integrated to .net)

  1. EMC
  2. Hummingbird
  3. Open Text
  4. Microsoft Windows SharePoint Services
  5. Xerox DocuShare
  6. UCM by Oracle
  7. FileNet by IBM
  8. Interwoven WorkSite
AlejandroR
  • 5,133
  • 4
  • 35
  • 45
  • I've worked on EMC (both eRoom and Documentum), Hummingbird DM, OpenText LiveLink, Xerox DocuShare & Microsoft SharePoint. I can tell you that SharePoint is the only one the is easy to work with .Net Framework. LiveLink has an acceptable API, but secure conenction is limited... eRoom/Documentum/DocuShare all have have terrible APIs.... – SaguiItay Oct 24 '10 at 01:04
0

I'm not completely sure what kind of integration you are after. If you're looking for a stand alone solution which has an API interface usable from .Net languages I can't help mentioning M-Files. Though I need to mention this recommendation might be extremely biased.

The system is commercial but there is a free version available with some limitations such as user amount etc. I believe.

The API is a pretty solid COM api which works quite smoothly through COM interop. It's strongly typed etc. so using it from .Net gives no troubles unlike some other COM apis. (Cough..Office..Cough) Internally the API is used to provide a web interface as an alternative to the native Windows integration so it's kept up to date and usable for this reason.

Mikko Rantanen
  • 7,884
  • 2
  • 32
  • 47
0

The old classic is Dot Net Nuke. There is a big community around the modules and of course you can write your own. Best of all it's open source.

  • 2
    I don't think DNN is particularly suited to DMS tasks. Just because you *can* write a module to do anything doesn't really mean much. It seems much more geared to WCM than DM. – Rex M May 05 '09 at 01:24
0

Take a look at SiteFinity, or Graffiti. I'm currently evaluating both of these as a potential solution for our site.

Paul Alexander
  • 31,970
  • 14
  • 96
  • 151
  • Those are both WCM systems, not DM systems. Do they have DM add-ons? – Rex M May 05 '09 at 01:29
  • The difference between CM and DM is a bit gray when it comes to .NET. Since they didn't specify any details I thought I'd point them to some other tools. Sitefinity comes mighty close to an online document system. – Paul Alexander May 05 '09 at 02:13
0

If cost is no issue and you can use a standard DMS pretty much out of the box (e.g. only minor custom development), Microsoft Office Sharepoint Server is great for document management and document-based team collaboration. Creating workspaces, integration with Office products (for example, you can save your Word and Excel work directly into your collaboration space on the Sharepoint server). For end-users who are already proficient in the Office suite, it's a very pleasant UX.

That having been said, there are two caveats - it is insanely expensive, and deep, core customizations are more than a little painful. Superficial widget-type customization is a breeze though.

Rex M
  • 142,167
  • 33
  • 283
  • 313
  • Windows Sharepoint Services is included with Windows 2008 Server, and it comes with all of the basic document management capabilities of MOSS. No additional licensing is required, provided you use it on the corporate intranet only (i.e. you don't need a web-facing server). – Robert Harvey Oct 05 '09 at 21:42