We don’t allow questions seeking recommendations for software libraries, tutorials, tools, books, or other off-site resources. You can edit the question so it can be answered with facts and citations.
Closed 9 years ago.
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
接受
或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论(3)
SharePoint 在文档管理、版本控制等方面做得非常好。它还具有大量 API,并且是比使用 VSS 的 COM 层更现代的方法。如果您将其编写为企业解决方案(专用服务器等),SP 将是一个很好的解决方案,但对于桌面或小型企业/SOHO 应用程序来说不太好。
SharePoint does a pretty good job of document management, with versioning, etc. It also has plenty of APIs and is a much more modern approach than using the COM layer for VSS. SP would be a good solution if you are writing this as an enterprise solution (dedicated server, etc), but not so good for a desktop or small-business/SOHO app.
实际上,在 Sharepoint 中使用文档版本控制非常容易。如果您设置新列表,您将能够直接在 SP 列表设置中定义附件和列表项的版本选项。
您还可以使用 SP Web 服务对版本控制进行更详细的控制。如果您计划从应用程序内进行所有文档访问,并且不想将用户推送到 Sharepoint 站点,我会使用此方法。这是一个很好的SP 版本控制入门教程
Its actually pretty easy to get rolling with document versioning in Sharepoint. If you setup a new list you will be able to define version options for attachments and list items right in the SP list settings.
You can also get a much more detailed control over versioning by using the SP webservices. If your planning on doing all of your document access from within your application, and don't want to have to push users into the Sharepoint site I would use this approach. Here is a good tutorial to get started with SP versioning
尝试塑料 SCM。它是分布式的,有一个很棒的 GUI,它也可以集中工作,您会发现大量的 .NET 程序集来挂钩您的代码。
替代文本 http://www.codicesoftware.com/images3mk/screenshots/visualize_4.JPG< /a>
Give a try to Plastic SCM. It's distributed, has a great GUI, it can work as centralized too and you'll find tons of .NET assemblies to hook your code.
alt text http://www.codicesoftware.com/images3mk/screenshots/visualize_4.JPG