SharePoint OOTB 功能与自定义开发
好吧，我总是问自己这个问题。
当谈到 SharePoint OOTB 功能 VS C# 自定义开发时，您的界限到底在哪里？
只需发表您的想法...（即使您认为这个问题很荒谬:-P）
Ok, I always ask this question to myself.
When it comes to SharePoint OOTB features VS C# custom development, where exactly do you draw the line?
Just post your thoughts... (even if you think this question is ridiculous :-P)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我不记得有一个项目其中 SP“OOTB”...
编辑：实际上，现在我“强迫”自己记住它，我认为这一切都变成了某种黑客行为或问题避免，以绕过某些限制或其他限制。区别在于在哪里遇到黑客攻击以及执行所述对策的难易程度。
I can't recall one single project where SP "OOTB"...
Edit: Actually, now that I am "forcing" myself to remember it, I think it all devolved to some hack or issue avoidance to get around some limitation or another. The difference is where the hack is encountered and how easy it is to perform said counter-measure(s).
不确定您将如何得到类似具体答案的信息，难道不应该根据具体情况来决定吗？
当然，这只是“如果定制开发的成本低于‘按原样生活’的成本”，那么就开发，或者不开发？
Not sure how you're going to get anything like a specific answer to this, shouldn't it be decided on a case by case basis?
Surely its just "If the cost of the custom development is less than the cost of 'living with it as is" then develop, or not?
在 SharePoint 中，有许多无需开发即可完成的自定义（如果您将“自定义开发”称为 C# 代码）。
使用 Sharepoint Designer 可以完成几件事，我不知道这些是否被视为自定义开发......
我已经使用 VS 创建了网站，使用 Designer 更改了基本内容，并且使用 WSS 作为 UI 创建了工作流程...所以这也取决于您想要完成的任务...
In SharePoint there are many customizations that can be done without having to develop (if you are referring to 'custom development' as C# code.
Several thing can be done using Sharepoint Designer, and I wouldn't know if those are to be considered custom development.....
I have created websites out of VS, changing basic stuff with Designer, and I've created workflows with WSS as the UI... so it also depend on what you want to accomplish...