在 sharepoint 2010 中为开发人员创建列表的最佳方法是什么？
在 sharepoint 上开发解决方案时，创建站点列表的最佳方法是： 1.Visual Studio中的解决方案功能 2.Sharepoint设计器 3.浏览器
考虑代码的可重用性和更容易的部署。
while developing a solution on sharepoint what's the best method to create site lists is it:
1.Solution features in Visual studio
2.Sharepoint designer
3 the browser
considering code reusability and easier deployments.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
在 Sharepoint 设计器中创建自定义列表非常简单。假设您不需要任何自定义字段，这是一个很好的起点。
在此创建您的定义，然后将其导出为模板。然后，您可以将此 wsp 导入到 Visual Studio 中以进行进一步自定义。然后，您可以按照任何其他包来部署它。将其放在 VS 中也很好，这样您就可以进行版本控制等。
这里有一个关于执行导入的很好的视频链接：
http://channel9.msdn.com/Blogs/funkyonex/Importing-SharePoint-Solution-Packages-WSP-into-Visual-Studio- 2010
编辑
这不太正确。您必须将该站点另存为模板 (wsp)，然后才能将其导入到 VS 中。您将看到一个向导，让您选择所需的列表。这有点痛苦，因为你必须取消选中所有内容 - 我看不到“取消选中所有内容”。
Creating custom lists in Sharepoint designer is quite straightforward. Assuming you don't need any custom fields, this is a good place to start.
Create your definition here, and then export it as a template. You can then import this wsp into visual studio for further customizing. You can then deploy this as per any other package. It's also nice to have this inside VS so you can version control / etc.
Here is a good video link on doing the import:
http://channel9.msdn.com/Blogs/funkyonex/Importing-SharePoint-Solution-Packages-WSP-into-Visual-Studio-2010
Edit
This isn't quite correct. You'll have to save the site as a template (wsp) that you can then import into VS. You'll get a wizard that lets you choose the list(s) you want. It's a bit of a pain as you have to uncheck everything - there's no 'uncheck all' that I can see.
为了快速获得结果，您无法使用浏览器。从自定义列表模板开始，您可以拥有一个闪亮的站点列表，其中包含查找字段、计算字段……但如果您想将其部署到其他地方，则需要将列表保存为列表模板。
如果您采用 Visual Studio 方式，则理想情况下必须首先创建一些网站栏，然后创建将使用这些网站栏的内容类型，然后基于该列表模板（以及最终此模板的实例）内容类型。所有内容都将打包在 WSP 中，您将能够部署所有内容，这显然需要更多工作，但由于 VS 2010，这比以前使用 SharePoint 2007 容易得多。
For quick results, you can't beat using the browser. Starting from a custom list template, you can have a shiny site list with lookup fields, calculated fields, ... but you'll need to save your list as a list template if you want to deploy it somewhere else.
If you go to the Visual Studio way, you'll ideally have to create some site columns first, then a content type that will use these site columns and then a list template (and eventually instance(s) of this template) based on that content type. Everything will be package within a WSP that you'll be able to deploy everything, that's obviously more work but thanks to VS 2010 this is a lot easier than it used to be with SharePoint 2007.