“ASP.NET MVC” Sharepoint 服务中的 CMS
我正在评估 ASP.NET MVC 中 CMS 的选项。 我目前正在开发一个需要 CMS 功能的多租户应用程序。 我一直在关注 N2、Mojoportal 等，但我也对 SharePoint Services 可以带来什么感兴趣。 具体来说，我不想要 SharePoint 网站，但我想潜在地使用 sharepoint 对象模型、数据库表等来形成 CMS 的核心。
SharePoint 可以做到这一点吗？还是我走错了路？ 我对此没有太多经验。
I'm evaluating the options for a CMS in ASP.NET MVC. I'm currently working on a multi-tenant app that requires CMS functionality. I've been looking at N2, Mojoportal etc, but I'm also interested in what SharePoint Services could bring to the table. Specifically I don't want a SharePoint site but rather I'd like to potentially use the sharepoint object model, db tables, etc. to form the core of the CMS.
Is this possible with SharePoint or am I going down the wrong path? I've not had much experience with it.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
SharePoint 不是 ASP.NET MVC 应用程序，它都是 Web 表单。 SharePointMVC CodePlex 项目尝试将 MVC 引入 SharePoint。
最终，您很可能迟早需要遵循“Web 表单”方式来使用 SharePoint 进行操作。 因此，如果需要 MVC，我不会使用 SharePoint。 然而，您的要求可能应该围绕客户想要什么，而不是使用什么技术？
我也不会采取仅使用 SharePoint 后端的方法。 请参阅此问题了解一些充分的理由。
SharePoint is not an ASP.NET MVC application, it's all web forms. There is the SharePointMVC CodePlex project that attempts to bring MVC to SharePoint.
At the end of the day you are very likely to need to follow the 'web forms' way of doing things sooner or later with SharePoint. So if MVC is a requirement I would not use SharePoint. However your requirements should probably be around what the customers want, not what technology to use?
I also wouldn't take the approach of using SharePoint's back end only. See this question for some good reasons why.