Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Dec 14, 2010 07:03 AM by marcind
Dec 14, 2010 12:25 AM|LINK
I'm working trying to realize a requirement where the pages should be 'configurable' at runtime (per client), stored in a database - a requirement that I have no say in
Anyway, the current plan is to use the Razor view engine and 'load' the 'pages' dynamically. I have a basic sample working using a VirtualPathProvider and VirtualFile that serves up Razor 'pages' on the fly.
The question I have if there is a better approach when I have the Razor 'pages' stored in a dB (or any other repository)?
There seems to be some constraints and concerns when I check other postings. For example:
'If a Web site is precompiled for deployment, content provided by a VirtualPathProvider instance is not compiled, and no
VirtualPathProvider instances are used by the precompiled site.' (from
Dec 14, 2010 07:03 AM|LINK
VirtualPathProvider is the way to go, and no, you can't do precompiled sites. Either the site is dynamically updatable from the database or it's precompiled.