ASP.NET MVC WAP、SharePoint Designer 和 SVN
所有，
我正在启动一个新的 ASP.NET MVC 项目，它需要一些内容管理功能。
管理内容的人员更喜欢使用 SharePoint Designer（FrontPage 的后续版本）来修改内容。我想让他们继续这样做。
问题是：
由于我希望这是一个 WAP，而不是一个网站项目，我如何才能让他们看到正在执行的更改，而不要求他们在本地计算机上安装 Visual Studio？我可以为控制器指定一个“默认”操作，以便给定像这样的 url <前><代码> /products/new_view_here
我可以让他们保存页面（视图）并在浏览器中查看它们，而无需执行签入/构建/部署过程吗？
我希望将他们的更改存储在 SVN 中； SharePoint 设计器似乎只直接支持 Visual SourceSafe（呃）。
到目前为止我提出的想法是
编写一个实现FrontPage 服务器扩展协议的HTTP 处理程序。这听起来很耗时，但我还没有查看协议规范。不过，它允许我在服务器端执行任何我想要的操作，包括将文件签入 SVN。
放弃 WAP，转而支持网站项目。然而，我不喜欢将源代码存在于服务器上。另外，MVC 可以在网站项目中使用吗？
肯定有人以前解决过这个问题吗？
All,
I'm starting a new ASP.NET MVC project which requires some content management capabilities.
The people who will be managing the content prefer to use SharePoint Designer (successor to FrontPage) to modify content. I'd like to allow them to keep doing that.
The issues are:
Since I'd like this to be a WAP, not a website project, how can I allow them to see their changes in action without requiring them to have Visual Studio on their local machines? Can I specify a "default" action for a controller so that given a url like
/products/new_view_hereCan I let them save pages (views) and see them in the browser without having to go through the check-in/build/deploy process?
I'd like their changes to be stored in SVN; SharePoint designer seems to only support Visual SourceSafe (ugh) directly.
The ideas I've come up with so far are
Write an HTTP handler that implements the FrontPage Server Extensions protocol. This sounds time consuming, but I haven't yet looked at the protocol spec. However, it would allow me to perform whatever operations I want on the server side, including checking files into SVN.
Ditch the WAP in favor of a website project. I do not like having the source present on the server, however. Also, will MVC work in a website project?
Surely someone has tackled this problem before?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这似乎相当复杂。如果他们要制作静态 html 页面，那么除了 Frontpage Extensions 之外的另一个选择是使用 FTP，因为我记得 Frontpage 通过 ftp 工作得很好。这样就可以解决问题的编辑部分。
我不知道确切的技术是什么，但是有一些服务可以监视文件系统的更改，您可以让它自动提交到 svn。
在这种情况下，我会将其提交到一个分支，也许对于每个设计师来说，然后当他们完成某些部分时，您或某个团队成员会将他们的更改合并到分支中，以便除了一系列机械的更改之外，还有有意义的历史记录提交将毫无价值。
另外，如果不是 FTP，那么 WebDAV 也可能是一个不错的选择。您可能还需要扩展 MVC 框架来编译每个页面浏览的模板，仅用于开发目的。
祝你好运！
This seems to be pretty complex. If they are going to be making static html pages then another option besides Frontpage Extensions is to use FTP, as I recall Frontpage worked nicely over ftp. Then that would smooth over the editing portion of the problem.
I don't know what the exact technology would be but there are services that will monitor a file-system for changes, you could have it automatically commit to svn.
In this case I would have it commit to a branch, maybe for each designer, and then when they have completed some portion you, or some team member then merges their changes into the branch so that there's meaningful history other than, a series of mechanical commits that will be worthless to read.
Also if not FTP, then WebDAV may be a good option too. You may also need to extend the MVC framework to compile the template each pageview just for development purposes.
Good Luck!