除 Sharepoint Designer 之外的 Sharepoint IDE
Sharepoint Designer (SD) 中的源代码控制可以说是一个更令人头疼的问题，而不是一个解决方案。特别是当多个人编辑相同的代码时。就我而言，我主要使用 SD 来编辑静态文件（css、js 和 html）。
我想这取决于共享点开发环境（当前使用开发虚拟机），但我遇到过冲突，SD不允许您签入/签出，不允许您保存......以及一大堆其他使掌握该工具变得困难的问题。
除了 SD 之外，您还使用哪些其他 IDE 进行共享点开发？最好是非 Microsoft 解决方案？有人成功完全停止使用 Sharepoint Developer 吗？
Source control in Sharepoint Designer (SD) is arguably more a headache than a solution; especially when more than one person is editing the same code. In my case, I am mostly using SD to edit static files (css, js and html).
I suppose it depends on the sharepoint development environment (currently using development VMs), but I have experienced conflicts where SD does not allow you to check-in/out, can not allow you to save.... and a whole host of other issues that makes mastering the tool difficult.
what other ides do you use for sharepoint development other than SD? Preferably a non-Microsoft solution? Has any one successfully stopped using sharepoint developer totally?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
不要使用 SharePoint Designer 推出自定义项 - 您可能会因 Windows 更新而丢失这些自定义项。如果您的所有自定义项都部署为功能，您可以使用 Visual Studio 实现完整的源代码控制。一旦你用VS检查了一些东西，你就可以使用SD2007进行风格调整。定制完成后，只需使用VS重新检查即可。
Do not use SharePoint Designer to push out customizations - you may lose these due to Windows Updates. If all your customizations are deployed as Features you can have full source control implemented using Visual Studio. Once you check something out with VS, you can then use SD2007 to make stylistic tweaks.When customizations are complete, just use VS to check back in.
尽管它不是与 SharePoint Designer 相当的工具，但 Mossquito 也可以让您省去一些麻烦。
Although it is not a comparable tool to SharePoint Designer, you may also save yourself some headaches with Mossquito.
对于 css/javascript/ html，我们使用 Aptana。它是 Eclipse 的衍生产品，支持 Eclipse 插件。 Aptana 允许您定义多个调试环境，因此您可以测试 FF、IE 6 - 8 等。只是警告您，有时我们在 Aptana 中进行测试，一旦我们导入了生成的标记在 SharePoint 中，我们遇到了奇怪的问题，因为 SharePoint 不支持标准 HTML。
For css/javascript/ html we use Aptana. it's a derivative of Eclipse and supports Eclipse plug-ins. Aptana allows you to define multiple debugging environments, so you can test for FF, IE 6 - 8, etc. Just to warn you, there have been times when we've tested in Aptana and once we've imported the resulting mark-up into SharePoint we have run into weird issues as SharePoint does not support standard HTML.