将库存系统从 ASP.NET MVC2 转换为 Sharepoint 2010，会出现什么问题吗？
在等待 Sharepoint 2010 安装时，我正在使用 ASP.NET 创建一个 Intranet 库存系统，使用 Visual Studio 2008 和 SQL Server 2005 中的 MVC2 和实体框架（我相信）对于一些客户端内容，我正在使用 jquery(日期选择器、一些 AJAX 发布等）。
库存系统包括库存设备清单以及结帐系统。
我的库存系统数据库结构使用 PK/FK 关系：
- 基本请求信息表
- 请求项目表
- 库存项目表
- 设备类型表
- 一个请求有一个或多个请求项目
- 一个请求项目是一个库存项目。
- 库存项目是一种设备类型。
在阅读有关 Sharepoint 2010 的内容时，我的印象是表格变成了列表，并且明确的 PK/FK 关系不再使用/可用。从本质上讲，我会失去正式 PK/FK 关系的一些好处。
话虽如此，将系统从 MVC2 转换为 Sharepoint 2010 会遇到多少麻烦？
我可以轻松地将 SQL Server 2005 表转换为 Sharepoint 2010 列表吗？公用事业？
我从头开始是不是更好？
Sharepoint 2010 对 jquery 友好吗？
While waiting for a Sharepoint 2010 install, I am creating an intranet inventory system using ASP.NET using the MVC2 and entity frameworks in Visual Studio 2008 and SQL Server 2005(I believe) For some of the client side stuff, I am using jquery(date picker,some AJAX posting, etc).
The inventory system includes a list of stocked equipment as well as a check-out system.
My DB structure for the inventory system makes use of PK/FK relationships:
- Table for basic request information
- Table for requested items
- Table for inventory item
- Table for equipment types
- A request has one or more requested items
- A requested item is one inventory item.
- An inventory item is one equipment type.
In reading about Sharepoint 2010, I am under the impression that tables become lists and explicit PK/FK relationships are no longer used/available. In essence, I would lose some of the benefits of formal PK/FK relationships.
With that said, how much trouble am I looking at to convert the system from MVC2 to Sharepoint 2010?
Can I convert from SQL Server 2005 tables to Sharepoint 2010 lists fairly easy? Utility?
Am I better off starting from scratch?
Is Sharepoint 2010 friendly to jquery?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
以下是一些快速解答：
列表是 SharePoint 中的本机数据存储。虽然它们具有关系数据库中的一些特征（关系、引用完整性），但它们不是关系数据存储。
编写一个从 SQL 表创建 SharePoint 列表的实用程序应用程序并不难。我认为您也可以使用 Access 或将数据导出到 Excel 并导入来完成此操作。
SharePoint 基于 WebForms 构建，不支持 MVC。您最多可以在您创建的自定义页面/部分中使用 MVP。
总体而言：虽然它们共享相同的基础技术，但构建 SharePoint 应用程序与构建传统的 ASP.NET 应用程序有着天壤之别。我强烈建议您在开始此项目之前花一些时间（从最终用户和开发人员的角度）学习 SharePoint。对我来说，我花了几个月的时间才充分了解 SharePoint 开发，从而能够胜任，并花了几个月的时间才感觉到自己的效率。
Here are some quick answers:
Lists are the native data store in SharePoint. While they have some characteristics you'll find in a relational database (relationships, referential integrity) they are not a relational data store.
It's not hard to write a utility application that creates SharePoint lists from SQL tables. I think you can also do this using Access or exporting data to Excel and importing.
SharePoint is built on WebForms and does not support MVC. At best you can use MVP in the custom pages/parts you create.
OVERALL: While they share the same underlying technology, building SharePoint applications is worlds away from building traditional ASP.NET applications. I highly suggest you spend some time learn to learn SharePoint (from both an end-user and developer point of view) before you start on this project. For me, it took a few months to understand SharePoint development well enough to be competent and several months before I felt I was effective.