Storing ASP.Net MVC Views in the Database

Question

For an ASP.Net MVC application, I'm interested in storing some views and/or partial views in the database so that a few semi-technical users can do some basic view logic. Does anyone have any tips or lessons from experience on doing this?

I know Phil Haack wrote a blog post on this about a year ago. He used IronRuby for scripting his views, (which would be fine for me). He created a quick proof-of-concept, but I can't find any other information on the topic.

Any ideas, thoughts, tips, etc would be appreciated.

Thanks!

Answer 1

Here you go. All that you need is to write a custom VirtualPathProvider and register it within the ASP.NET hosting environment. Works also with classic WebForms.