从自定义 ASP.NET 应用程序迁移到 Sharepoint Services
我们公司有一个用于客户信息数据库的 ASP.NET 应用程序。 该应用程序一开始规模很小，但在没有适当设计的情况下不断发展。 现在应该开发该应用程序的新版本，这基本上意味着从头开始设计和实现它。 该公司有兴趣在未来使用 Microsoft Sharepoint 服务，并建议使用该客户数据库应用程序进行试点。
所以我的问题是：
数据库驱动的应用程序适合 WSS 吗？ 大多数情况下，该应用程序会对数据库执行 CRUD 操作并创建报告。
Our company has an ASP.NET application for customer information database. The application started small but has grown without proper design. Now a new version of the app should be developed, which basically would mean designing and implementing it from scratch. The company is interested in making use of Microsoft Sharepoint Services in future and it has been suggested to pilot it with this customer database application.
So my questions is:
Is database driven application something WSS is good for? Mostly the app would perform CRUD-operations on the database and also create reports.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
我同意 Greg 的观点，因为我不一定建议将数据放入 SharePoint 列表中（这就是 Greg 可能的假设）。 但我的简短回答是“也许”。
这是长答案...
SharePoint 在 ASP.NET 上运行，因此它应该满足您的需求。 您可能会编写位于 SharePoint 中的 ASP.NET 网页来访问数据库，或者编写位于 SharePoint 中的 Web 部件来访问您的数据库。
您可以考虑使用 BDC 来读取/检索数据，但这需要 MOSS Enterprise 并且不会提供 CRUD 的 CUD 部分。 其他工具（例如 CorasWorks DIT）可能会有所帮助，但我怀疑自定义 Web 部件或页面是您的最佳选择。
您可以从 SharePoint 中获得很多好处，例如授权，或许还可以将您的数据与 SharePoint 列表数据集成、配置、搜索等。SharePoint 是否会提供很多功能，这实际上取决于您的应用程序的性质。益处。
I agree with Greg in that I wouldn't necessarily recommend putting your data in SharePoint lists (this is what Greg may be assuming). But my short answer would be "maybe".
Here's the long answer...
SharePoint runs on ASP.NET so it should accommodate your needs. You would likely be writing ASP.NET web pages that live within SharePoint that access your database or writing web parts that live within SharePoint that access your database.
You could consider the BDC for reading/retrieving data, but that requires MOSS Enterprise and won't provide the CUD part of CRUD. Other tools like CorasWorks DIT may help, but I suspect that custom web parts or pages are the way to go for you.
There are plenty of benefits you can get from SharePoint such as authorization and maybe things like integration of your data with SharePoint list data, provisioning, search, etc. It really depends on the nature of your application as to whether SharePoint will provide much of a benefit.
简短回答：不。
详细回答：
有合作吗？ 数据的支持文档？ 工作流程？ 如果不是，那么确实没有任何理由通过 SharePoint 托管它 - 您不会获得太多收益。
此外，请记住，SharePoint 列表可能看起来像表格，但事实并非如此 - 列表没有关系方面 - 没有加入，没有级联更新/删除等。如果数据报告是您应用程序的重要组成部分，这可能会成为问题。
您可以将数据存储在外部并使其在 SharePoint 中显示为只读列表，但如果您不使用任何其他 SharePoint 功能，您仍然会遇到很多麻烦。
Short answer: No.
Long answer:
Is there any collaboration? Supporting documentation for the data? Workflow? If no, then there really isn't any reason to host it through SharePoint - you won't be gaining much.
Additionally, keep in mind that the SharePoint lists may look like tables, but they aren't - there is no relational aspects of the lists - no joining, no cascading updates/deletes, etc. This may be a problem if data reporting is a big part of your app.
You can store the data externally and have it appear as read-only lists in SharePoint, but you're still jumping through a lot of hoops if you're not using any of the other SharePoint features.
柯克（Kirk）打败了我，并且说得比我更好:)
另一件需要考虑的事情是流程中工作流程的可能性。 例如，如果您需要在添加新联系人（后续呼叫等）时启动流程，那么 SharePoint 可以提供很大的优惠或好处。
也许混合解决方案是合适的。 用于 CRUD 和 SharePoint 集成的自定义应用程序，提供有意义且提供价值的部分。
为了使用 SP 而构建 SP 可能不是一个好主意。
Kirk beat me to punch and said it better than I would have anyway :)
Another thing to consider is the possiblity of workflows in your process. For example, if you need to start a process when a new contact is added (a follow-up call, etc.), then SharePoint provides a great deal or benefit.
Perhaps a hybrid solution would be appropriate. A custom app for your CRUD and SharePoint integration for the pieces that make sense and provide value.
Building in SP for the sake of using SP probably isn't a good idea.
我们有一个在 MOSS 2007 中运行的 ASP.NET 应用程序。虽然我们几乎不使用 SharePoint 的任何功能，但我们确实利用了 SharePoint 的安全模型、导航 Web 部件（我们使用 CorasWorks）、集成的 Reporting Services 和工作流。 至少，SharePoint 功能有一天可供我们使用。
我们所有的应用程序数据都位于其自己的 SQL Server 数据库中。 我们不会在 SharePoint 内容数据库中存储任何内容。
We have an ASP.NET application that runs in MOSS 2007. While we barely use any of SharePoint's features, we do get the advantage of SharePoint's security model, navigation webparts (we use CorasWorks), integrated Reporting Services, and workflows. In the very least, SharePoint features are there for us to use someday.
All of our application data is in its own SQL Server database. We don't store anything in the SharePoint content database.