在生产环境中使用 SharePoint Designer 有哪些风险？
我正在寻求有关在生产环境中使用 SharePoint Designer 的一些反馈（这里我指的是 SharePoint 2007）。 SharePoint 社区中似乎存在相互矛盾的观点，一些人主张该工具是“高级用户”自定义布局和构建工作流程的有效手段，而其他人则认为有效使用 SPD 意味着在生产环境中进行开发，这种情况不应该发生，句号。
这个工具显然是针对通常不会经历开发/阶段/产品的完整应用程序生命周期的用户类型，特别是当他们只想更改颜色或在页面上插入横幅时。我清楚地听到“不要在生产中开发”的信息，但如果是这样的话，SPD 会在哪里呢？直接在生产环境中使用是否存在实际风险？是否应该被阻止？如果是这样，谁是目标受众？还有空间吗？
I’m after a bit of feedback with regards to using SharePoint Designer in production environments (I’m talking SharePoint 2007 here). There seem to be conflicting views amongst the SharePoint community with some advocating the tool as a valid means of “power users” customising layouts and building workflows whilst others take the view that using SPD effectively means developing in a production environment and it shouldn’t happen, full stop.
This is a tool obviously targeted at the type of users who are not typically going to go through a full application lifecycle of dev / stage / prod, particularly when they’re only looking to change a colour or insert a banner on a page. I hear the “don’t develop in production” message loud and clear but if that’s the case, where does it leave SPD? Is there a practical risk from its direct usage in a production environment? Should it be blocked? If so, who’s the intended audience and is there any place left for it at all?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我在实际环境中使用过共享点，我强烈建议不要使用它。
它还给我留下了损坏的文件。
最后，虽然这取决于你推动它的深度，但如果你打算坚持设计模式或使用它来管理你的工作流程模式，那么就轻轻地走吧。
I have used sharepoint in a live enviroment and I would highly advise against it.
It has also left me with corrupted files.
In the end though it depends on how in depth you are pushing it, if you are going to stick in deisgn mode or use it for managing your workflow patterns then go ahead just tread lightly.
有时我们必须使用它。如果你小心的话，你可以避免前面答案中描述的所有陷阱。我通常会在修改之前保留页面代码的副本，以便在必要时可以回滚。
请记住，将页面设为非幻影化也会对性能产生影响。一旦您在设计器中修改了页面，它就会与文件系统上保存的站点定义副本分离，并且每次都需要从数据库而不是服务器缓存加载，他们说这可能会使页面变慢约 10-15%加载。
Occasionally we have to use it. If you are careful, you can avoid all the pitfalls as described in the previous answer. I usually keep a copy of the page code prior to modifications so I can roll back if necessary.
Please keep in mind the performance impact of making your pages unghosted as well. Once you modify a page in the designer it is detached from the site definition copy kept on the file system and needs to be loaded every time from the DB instead of the server cache, they say it could make the pages about 10-15% slower to load.
对于 SharePoint 中的自定义开发，我建议使用解决方案包或 SharePoint Designer，但不能同时使用两者。我更喜欢在具有开发/测试/生产服务器的环境中使用解决方案包，但如果没有这样的环境，我可能会倾向于 SharePoint Designer 而不是解决方案包。是的，SharePoint Designer 可能会将网站置于不良状态，但速度可能不如解决方案包的初始开发迭代那么快。
使用 SharePoint Designer 时，您肯定需要控制谁有能力自定义网站。 SharePoint Designer 2007 会自动受到限制，因为您需要拥有许可证才能安装它。虽然许可可能很麻烦（而且价格昂贵），但它确实有一个好处，可以让您精确控制受众。
编辑：
SharePoint Designer 2007 是 也是免费的。因此，对于 SharePoint 2007 和 SharePoint 2010，您需要确保环境被锁定，以便临时用户不会对网站进行未经授权的设计更改。
For custom development in SharePoint, I recommend using either Solution Packages or SharePoint Designer, but not both. I prefer Solution Packages in an environment that has dev/test/prod servers, but without such an environment, I would probably lean toward SharePoint Designer over Solution Packages. Yes, it is possible for SharePoint Designer to put a site in a bad state, but not as quickly as the initial development iterations of a Solution Package can.
When using SharePoint Designer, you definitely need to control who has the ability to customize the site. SharePoint Designer 2007 is automatically limited because you needed to have a license in order to install it. While licensing can be a hassle (and expensive), it does have the benefit of giving you precise control over your audience.
EDIT:
SharePoint Designer 2007 is free as well. So for both SharePoint 2007 and SharePoint 2010, you will want to make sure that the environment is locked down so that casual users are not making unauthorized design changes to the site.