从开发人员的角度来看，Sharepoint 开发是什么? [英] What is Sharepoint development from a developers point of view?

问题描述

这些天我听到很多关于 Sharepoint 的讨论，但我无法通过所有企业和营销术语准确掌握它的含义.亲自尝试似乎也太麻烦了(您不能免费下载几个沉重的软件包).

I hear a lot of talk about Sharepoint these days, but I'm having problems grasping exactly what it is through all the enterprise and marketing jargon. Trying it out hands-on seems too much of a hassle as well (several heavy software packages that you can't just download for free).

有人可以对 Sharepoint 是什么进行一个很好的开发者对开发者的描述吗?我特别想知道 Sharepoint 开发人员通常会做什么.

Could someone give a good developer-to-developer description of what Sharepoint is? I'd especially like to know what Sharepoint developers generally do.

推荐答案

== Edit 2017 ==

这是一篇相当古老的帖子，SharePoint 在过去几年发生了很大变化.原始帖子的大部分内容仍然有效，但有些内容仅适用于您在 SharePoint 的未来似乎倾向于 SharePoint Online 的本地安装的情况下.话虽如此，但大多数功能仍然存在，但有一些改进.

This is a fairly old post and SharePoint have changed a lot the past years. Most parts of the original post are still valid but some would only apply if you do on premise installations where the future of SharePoint seem to lean towards SharePoint Online. That being said, most functionality are still there with some improvements.

== 原帖 ==

SharePoint 是一个非常复杂的 CMS(内容管理系统)，具有许多不错的 BSS(业务支持系统)功能.它有很多优点，很难限制要提及的内容.然而，一些显而易见的事情是，您可以在同一台服务器上混合如此多的环境"，这些环境被分隔为站点.

SharePoint is a very complex CMS (Content Management System) with a lot of nice BSS (Business support system) features. There are so many advantages of it that it's hard to limit what to mention. However, some of the obvious stuff would be that you can mix so many "environments" at the same server, these environments are separated as sites.

我所说的环境是什么意思?

What do I mean by environments?

假设您经营一家物流公司，并且厌倦了拥有这么多不同的系统只是为了让您的业务正常运转.许多系统也有不同的供应商，因此公司周围的生态系统也变得同样复杂，SharePoint 来救援，因为它是一个实际上可以托管所有必需环境的系统.例如.

Let's say you run a logistics company and are sick of having so many different systems just to keep your business up and running. Many of the systems also have different providers so the ecosystem around the company gets equally complex as well, here comes SharePoint to the rescue since it's a system that actually can host all required environments. In example.

• 外部网页，由 SharePoint 或集成网页托管
• 订单管理
• 客户支持和票务
• 货物处理
• 具有文档管理功能的 Intranet 站点

这些环境中的每一个都可以受益于 SharePoints 内置功能，例如工作流和自定义内容类型.

Each and every of these environments can benefit from SharePoints built-in features like workflows and custom content types.

我认为选择 SharePoint 的首要原因是它可以存储不同类型的数据.如果您计划每秒处理 100 万个事务，即使性能可以通过场中的多台服务器大幅升级，它也不是一个可供选择的系统.

I'd say that the foremost reason to choose SharePoint would be it's versatility of storing different types of data. It's not a system to choose if you are planning one million transactions each second even if the performance can be greatly upgraded with several servers in a farm.

我作为开发人员的观点是，SharePoint 几乎全是关于列表、库和元数据存储，因为它是保存大部分数据的地方.这是您需要学习并了解如何构建数据以及如何实施信息模型的内容.

My point of view as a developer is that SharePoint is pretty much all about the lists, libraries and the metadata store since it's where most of the data is kept. This is something you need to learn and to understand how to structure your data and how you'll implement your information model.

在我的世界中，最常见的任务是将 SharePoint 与外部 CMS(如 EPIServer 或 Joomla)集成，以建立一个集成，使访问者能够将来自 Web 的消息直接发送到 SharePoint.然后，这些分配会导致创建一个工作流，当客户支持/销售人员或其他任何人收到此消息时，该消息将发生什么，一直到差事可以结束.完成此操作后，我可能会使用 mschart 在自定义 Web 部件中构建一些图表，显示一些销售数据或支持差事的统计信息.目前我正在计划使用 SharePoint 作为网上商店的数据结构.又来了，多功能性！

The most common assignment in my world would be integration SharePoint with an external CMS, like EPIServer or Joomla, to set up an integration where the visitors shall be able to send messages from the web directly into SharePoint. These assignments then trails into creating a workflow what will happend with this message when it's received by the customer support / sales staff or whatever, all the way until the errand can be closed. When done with this I might build some graphs in a custom web part using mschart displaying some sales data or statistics of support errands. Currently im planing the data structure using SharePoint as a webshop. And there you go again, versatility!

如果您要进行集成，SharePoint 中还有一个非常强大的 API.我自己参与了 SharePoint 的 ADO.NET 连接器的生产，它将 SharePoint 变成了 SQL 服务器，使开发人员能够跳过使用 CAML.而且，还有很多其他很酷的工具.

There is also a very powerful API in SharePoint if you are into integrations. I am myself involved in the production of an ADO.NET Connector for SharePoint which turns SharePoint into a SQL server enabling developers to skip using CAML. And, there are plenty of other cool tools out there.

不要忘记使用 SharePoint 的第二大优势.您可以专注于前向开发，后端已经存在.

Let's not forget the second biggest advantage of using SharePoint. You can focus on forward development, the backend is already there.

这篇关于从开发人员的角度来看，Sharepoint 开发是什么?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！