如果成本不是问题，并且您几乎可以立即使用标准 DMS（例如，仅进行少量自定义开发），Microsoft Office Sharepoint Server 非常适合文档管理和基于文档的团队协作。 创建工作区，与 Office 产品集成（例如，您可以将 Word 和 Excel 工作直接保存到 Sharepoint 服务器上的协作空间中）。 对于已经精通 Office 套件的最终用户来说，这是一个非常令人愉快的用户体验。
话虽如此，有两个警告：它非常昂贵，而且深度的核心定制非常痛苦。 不过，表面小部件类型的定制很容易。
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.
我不完全确定你想要什么样的整合。 如果您正在寻找一个独立的解决方案，该解决方案具有可从 .Net 语言使用的 API 接口，我忍不住要提到 M 文件。 尽管我需要提到这个建议可能非常有偏见。
该系统是商业的，但有一个免费版本，但有一些限制，例如用户数量等。我相信。
该 API 是一个非常可靠的 COM API，通过 COM 互操作可以非常顺利地工作。 它是强类型的等等，因此与其他一些 COM api 不同，从 .Net 使用它不会带来任何麻烦。 （咳..Office..咳）在内部，API 用于提供 Web 界面作为本机 Windows 集成的替代方案，因此它保持最新且可用。
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.
发布评论
评论（5）
查看 SiteFinity 或 涂鸦。 我目前正在评估这两者作为我们网站的潜在解决方案。
Take a look at SiteFinity, or Graffiti. I'm currently evaluating both of these as a potential solution for our site.
如果成本不是问题，并且您几乎可以立即使用标准 DMS（例如，仅进行少量自定义开发），Microsoft Office Sharepoint Server 非常适合文档管理和基于文档的团队协作。 创建工作区，与 Office 产品集成（例如，您可以将 Word 和 Excel 工作直接保存到 Sharepoint 服务器上的协作空间中）。 对于已经精通 Office 套件的最终用户来说，这是一个非常令人愉快的用户体验。
话虽如此，有两个警告：它非常昂贵，而且深度的核心定制非常痛苦。 不过，表面小部件类型的定制很容易。
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.
以下是当今企业中一些最常见的 DMS 的列表。
（它们都可以集成到 .net）
Here is a list of some of the most common DMS found in enterprises nowadays.
(they all could be integrated to .net)
我不完全确定你想要什么样的整合。 如果您正在寻找一个独立的解决方案，该解决方案具有可从 .Net 语言使用的 API 接口，我忍不住要提到 M 文件。 尽管我需要提到这个建议可能非常有偏见。
该系统是商业的，但有一个免费版本，但有一些限制，例如用户数量等。我相信。
该 API 是一个非常可靠的 COM API，通过 COM 互操作可以非常顺利地工作。 它是强类型的等等，因此与其他一些 COM api 不同，从 .Net 使用它不会带来任何麻烦。 （咳..Office..咳）在内部，API 用于提供 Web 界面作为本机 Windows 集成的替代方案，因此它保持最新且可用。
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.
旧的经典是 Dot Net Nuke。 围绕这些模块有一个很大的社区，当然您可以编写自己的社区。 最重要的是它是开源的。
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.