MOSS 网站定义、功能和移动网站集
普遍的共识是，MOSS 发布网站的开发应该使用网站定义、解决方案、功能来完成，但由于项目时间尺度，我们必须使用 SharePoint UI 和 SPD 来完成所有列表/网站栏/内容类型/母版页开发。 然后，我们使用内容部署向导来迁移开发中的所有内容。
完成此操作后，未来的计划可能是在考虑到预算的情况下，更改已构建的内容以使用站点定义和功能，以符合最佳实践。
有没有人做过类似的事情，或者有关于如何最好地规划这一点的建议？
亲切的问候
The general consensus is that devlopment of MOSS publishing sites, should be done using site definitions, Solutions, Features but due to project timescales we had to do all list/site column/content type/master page development using the SharePoint UI and SPD. We then used the contentdeployment wizard to migrate everything from devlopment.
Having done this, the future plan is to possibly, given the budget, change what has been built to use a site definition and features to get in line with best practices.
Has anyone done anything similar or have any tips on how best to plan for this?
Kind Regards
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这在一定程度上取决于您的解决方案的规模和复杂程度。 我开始参与的一个项目也遇到了同样的情况。他们最初开始在 SharePoint Designer 中完成所有操作。 但当我投入到这个项目中时，我决定放弃所有这些更改，从需求开始，在 Visual Studio 中将所有内容构建为站点定义/解决方案/功能。 在这种情况下，这是可行的，因为定制并不太复杂。
您可以查看 SharePoint 解决方案生成器，看看它是否也能帮助您。 它至少可以给你一个良好的起点。
This is somewhat dependent on how large and complex your solution is. I was in the same situation with a project I started to work in. They initially started to do everything in SharePoint Designer. But when I was thrown in to the project, I decided to scrap all those changes, starting from the requirements and build up everything as site definitions/solutions/features in Visual Studio. In this case, it was feasible since the customizations were not too complex.
You can take a look at the SharePoint Solutions Generator, to see if that could help you as well. It can give you at least a good starting point.