Sharepoint 2010 Web 应用程序开发适宜性评估/评估
我想知道哪些类型的应用程序适合在 Sharepoint 2010 之上开发，哪些应用程序不不应构建在其之上。那么何时接受/避免使用 Sharepoint 2010 作为新 Web 应用程序的开发平台。
附录
作为 Sharepoint 开发专家，您是否会选择它作为您下一个具有以下特征的企业应用程序的平台：
- 处理器密集型
- 用于输入和管理数据的大量各种屏幕
- 许多复杂的业务流程
- 无需更改 UI（即重新定位部件）
- ERP整合
- 等
我是一名 Asp.net MVC（前 Web 表单）开发人员，想知道通常的多页半复杂 Web 应用程序（内网/外网）是否应该构建在 Sharepoint 2010 之上以及为什么（如果是或否）。
I would like to know what kind of applications are suitable to be developed on top of Sharepoint 2010 and which should not be built on to of it. So when to embrace/avoid Sharepoint 2010 as a development platform for new web applications.
Addendum
Would you as a sharepoint development specialist choose it as a platform for your next enterprise application with these characteristics:
- processor intensive
- lots of various screens for entering and managing data
- many complex business processes
- no need to change the UI (ie. reposition parts)
- ERP integration
- etc.
I'm an Asp.net MVC (former web forms) developer and would like to know if usual multi-page semi complex web applications (intra/extra-net) should be built on top of Sharepoint 2010 and why (if yes or if no).
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我首先要说的是，sharepoint 是可用性、开发和性能的噩梦。我见过很少有用户喜欢它，创建强大解决方案的开发方法就像在滚木时玩弄保龄球瓶，而且框架中有太多额外的膨胀，在其中构建高性能解决方案几乎是不可能的。
尽管如此，它仍然非常适合构建 Intranet 解决方案，例如接入业务系统的仪表板。您可以在其中做很多事情，而无需编写实际代码，因此团队房间和基本数据收集活动非常适合。
我不会在其上构建一个面向公众的公司网站，该网站要么是静态的，要么提供服务。
I will preface this by saying that sharepoint is a usability, development and performance nightmare. I've met few users who enjoy it, the dev approach to create robust solutions is like juggling bowling pins while log-rolling and there is so much extra bloat in the framework that building a high-performance solution in it is almost impossible.
Despite this, it's very good for building intranet solutions like dashboards that tap into line of business systems. You can do quite a bit in it without ever having to write actual code, so team rooms and basic data collection activities are a good fit.
What I wouldn't build on it is a public-facing company website that is either static or provides a service.
SharePoint的开发工具在2010版本中得到了很大的改进。如果您了解 ASP.NET MVC 但不了解 SharePoint，那么您可能会在 MVC 中更快地完成应用程序，但问题是之后会发生什么。 SharePoint 可以轻松创建非开发人员可以稍后以某种方式修改的应用程序。
例如，您可以：
另一方面，SharePoint 为您提供了许多可能会妨碍您的内容（有大量的数据库、IIS 站点、服务等），并且您可能必须更加努力才能对应用程序实现与 MVC 中相同级别的视觉和功能控制。而且单元测试非常困难。
所以基本上这是一个你希望应用程序有多灵活以及在什么级别的问题。我不会将 SharePoint 2010 用于所有事情。这个网站 - Stack Overflow - 是 SharePoint 阻碍的应用程序示例。
不过，为了回答您的其他问题，如果您的客户想要的话，我没有任何非常有力的理由不使用它（除此之外，这将需要更长的时间，因为您必须学习 SharePoint）。考虑到 SharePoint 2010 使用起来非常有趣，我会找借口去了解它。这样你以后就能更好地争论它的赞成和反对。
The development tools for SharePoint have improved a lot in the 2010 version. If you know ASP.NET MVC but not SharePoint, you'll probably get your application done faster in MVC, but the question is what will happen to it afterwards. SharePoint makes it easy to make applications that non-developers can modify later in some way.
For instance, you can:
On the other hand, SharePoint gives you lots of stuff that may just be in the way, (there's a ton of databases, IIS sites, services, etc.), and you may have to work harder to achieve the same level of visual and functional control over your application as you would in MVC. And unit testing is pretty hard.
So basically it's a question of how flexible you want the application to be, and at what level. I wouldn't use SharePoint 2010 for everything. This site - Stack Overflow - is an example of an application where SharePoint would just be in the way.
To answer your other question, though, I don't have any very strong arguments not to use it, if that's what your client wants, (apart from that it will take longer, because you'll have to learn SharePoint). And considering that SharePoint 2010 is pretty fun to work with, I'd take the excuse to get to know it. Then you'll be better able to argue for and against it in the future.
这是一个陡峭的学习曲线，Sharepoint 2007 并没有多大帮助。您要么必须调整开箱即用的内容，要么做大量工作才能获得可用的环境（读取空白母版页、支持 xhtml、jquery 支持等的控件和布局）
如果您有一个文档或图像丰富的系统，或者您的客户急需一个典型的开箱即用的外联网/内联网，那么它是一个很好的工具。
否则，花费大量精力来加快速度可能是不值得的。
编辑：Asp.net 作为默认设置。这取决于您是否需要门户/内容管理/文档和图像共享。如果您只是创建定制应用程序，那么您就不需要它。如果您要创建一个具有资源/文档共享功能的社区，那么 Sharepoints 就是您的最佳选择。您仍然可以在 Sharepoint 中执行 ASP.NET - 这就是它的构建基础。
Its a steep learning curve and Sharepoint 2007 didnt help out much. You either had to tweak what came out the box or do a lot of work to get a useable environemnt (read blank master pages, controls and layouts that supported xhtml, jquery support etc)
If you have a system that is document or image rich, or your customer has the need for a typical out of the box extranet/intranet in a hurry then it is a good tool.
Otherwise its a lot of effort to get up to speed that may not be worth it.
EDIT: Asp.net as a default setting. It depends if you need a portal/content management/document and image sharing. If you are jsut creating bespoke applications you jsut dont need it. If you are creating a community with resource/document sharing, then Sharepoints the way to go. You can still do ASP.NET inside Sharepoint - thats what it is built on.