我需要了解 Sharepoint 的哪些部分才能构建面向公众的网站？
我正在建立一个面向公众的网站，该网站执行以下操作。 用户登录。 然后查看他们的客户列表。 他们点击客户即可查看他们过去的购买情况、订购、更改等。 顺便说一句，这不是一个购物网站。 这是一个简单的查找工具。
请注意，网站访问的所有数据均位于 SQL 数据库中 - 没有办公文档。此外，登录不使用 VPN 或类似设备上的用户 Windows 凭据。
通常我会使用标准 ASP.NET MVC 网站来构建它。 然而客户表示他们想要使用 Sharepoint。
据我了解，Sharepoint 用于作为协作工具的工作流程和网站，例如您可以在此处看到的组件 http://www.sharepointhosting.com/sharepoint-features.html
以下是我的问题：
我是否正确地说 WSS 完全不适合这项任务，因为它带来的开销没有任何好处？
如果我必须使用它，我需要 WSS 还是 MOSS？
如果我必须使用它，我是否正确地说该网站将包含：
列表项
a) Web 部件
b) 以及自定义站点布局。如何创建其中之一？
附录：专业 SharePoint 2007 Web 内容管理开发这本书看起来是一个好的开始
I am building a publicly facing website that does the following.
Users log in.
And then view a list of their customers.
They click on a customer to view their past purchases, order them, change them etc.
This is not a shopping site by the way.
It is a simple look up tool.
Note that none of the data accessed by the website is in anything other than a SQL database - no office documents. Also, the login does not use users Windows credentials on a VPN or something like that.
Typically I would build this using a standard ASP.NET MVC website.
However the client says they want to use Sharepoint.
As I understand it, Sharepoint is used for workflow and websites that are collaboration tools such as the components you can see here http://www.sharepointhosting.com/sharepoint-features.html
Here are my questions:
Would I be right in saying that WSS is completely inappropriate for this task as it comes with an overhead that provides no benefits?
If I had to use it, would I need WSS or MOSS?
If I had to use it, would I be right in saying the site would consist of :
List item
a) Web Parts
b) And a custom site layout. How do I create one of these?
Addendum:The book Professional SharePoint 2007 Web Content Management Development looks like a good start
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
1.) 我同意 SharePoint 非常不适合这项任务。有几个原因：
SharePoint 占有一席之地 - 作为公司的内部文档管理，它非常有帮助、内部网和工作流程/审批系统——但它不太适合自定义代码或互联网使用。
2.) 我相信互联网许可证需要 MOSS（如上面的链接所示）。
3.) SP开发不像典型的关系数据库系统（例如，它使用平面的、非规范化的表）。如果您的 SQL 符合 SharePoint 的思维方式，您也许能够使用 SharePoint 设计器。您更有可能需要使用 Visual Studio 在 ASP.NET 中创建自定义 Web 部件。
希望这将是一些合理的论点，您可以用来帮助客户了解 SharePoint 为何不适合该任务...事实上，我预计只有第一点（许可成本）就能改变他们。
1.) I agree that SharePoint would be quite inappropriate for this task. A few reasons:
SharePoint has it's place--it can be remarkably helpful as a company's internal document management, intranet, and workflow/approval system--but it is not well suited for custom code nor Internet use.
2.) I believe MOSS would be required for the Internet license (as in the link above).
3.) SP development is not like typical relation database systems (for example, it uses flat, unnormalized tables). If your SQL matched the SharePoint way of thinking, you might be able to connect to your database as an external List using SharePoint Designer. More likely you would need to use Visual Studio to create a custom Web Part in ASP.NET.
Hopefully this'll be a few reasonable arguments you can use to help the customer see how SharePoint is inappropriate for the task... In fact, I expect just the first point (the cost of licensing) will turn them.
从技术上讲，您可以使用 WSS 来完成此任务，但 MOSS 有更多旨在构建面向公众的网站的功能。我想到了发布基础设施。它具有 CQWP，使您能够构建在以下环境中表现良好的自定义界面SharePoint。对于 SharePoint，在可扩展性方面存在潜在的挑战。如果您很了解该平台，那么执行您所建议的操作将是一项非常快速的任务。如果您不太了解 SharePoint 和底层系统，您可能会面临挑战。
您不想使用 SharePoint Designer 构建最终应用程序。它的行为可能会导致可伸缩性方面的重大问题。您想要创建一个包含许多可以轻松部署到 SharePoint 的功能的 SharePoint 解决方案。走这条路并不能缓解性能问题，但您将更接近正确的解决方案。您可以将自定义用户界面元素打包为 CQWP 或编写 Web 部件。我个人更喜欢编写Web 部件。
您可以在母版页中进行总体网站设计。站点内的页面将继承此页面。如果您有 MOSS，那么您可以创建所谓的发布页面< /a> 其中包含您的 Web 部件。这些在 WSS 中不可用，这就是为什么人们建议不要将其用于公共网站。
要确定 SharePoint（任何版本）是否值得，您需要了解他们是否将使用任何核心功能。如果一切都是自定义的，并且您不会在部署中使用任何工作流程或文档管理功能，那么我会远离。要了解您是否希望从开发角度进一步使用 SharePoint，请查看 WSS 开发人员实验室。我最近使用该网站上的材料为我的雇主开设了一个介绍课程。它们已经过时了，需要更多有关最佳实践的信息，但它们提供了一种快速方法，让您可以尝试一下并决定是否要进一步进行。
You can technically use WSS for this task but MOSS has more features aimed at building public facing websites. The publishing infrastructure comes to mind. It has has the CQWP which enables you to build custom interfaces which perform well in SharePoint. With SharePoint there are potentially challenges around scalability. If you know the platform well then doing something like what you have suggested would be a pretty quick task. If you don't know SharePoint and the underlying system well you could face challenges.
You do not want to approach building the final application with SharePoint Designer. It has behavior which can cause major problems with scalability. You want to create a SharePoint Solution comprising a number of features which can be easily deployed to SharePoint. Going this route does not alleviate performance problems but you are going to be closer to the right solution. You can package up the custom user interface elements as CQWPs or write Web Parts. I personally prefer to write Web Parts.
You do the overall site design in a Master Page. Pages within a site are then inheriting from this. If you have MOSS then you can create what are called publishing pages which contain your Web Parts. These are not available in WSS which is why people recommend against it for public websites.
To decide whether SharePoint (any version) is worth it, you need to find out if they are going to use any of the core features. If everything is going to be custom and you are not going to make use of any workflow or document management features in your deployment then I would stay away. To see whether you want to go further with SharePoint from a development perspective, take a look at the WSS developer labs. I recently ran an intro course at my employer using the materials from that site. They are dated, and need more info on best practices but they provide a quick way for you to dip a toe in the water and decide whether you want to go any further.
1）对于您所描述的核心功能，SharePoint不会添加任何内容，但是如果您在SharePoint上构建它，则它允许您的客户“免费”在核心之外添加许多功能，例如：
所以总而言之，除非您有更好的框架可以使用，然后使用 SharePoint
2) WSS 就是您现在所需要的一切
3) 您目前的主要交付成果将是：
1) For the core functionality as you describe it SharePoint isn't going to add anything, BUT if you build it on SharePoints premisses it allows your client to add a lot of functionality outside the core for "free" like:
So all in all unless you have a better framework to use then use SharePoint
2) WSS is all you need for now
3) Your main deliverable for now would be:
确实。好吧，并不是不合适，但它也没有添加任何东西..但也许在未来？
WSS 就足够了
True. Well not inappropriate but it doesn't add anything either.. but maybe in the future?
WSS is enough