How to use one action to render views from database

Question

0.00/5 (No votes)

See more:

I have a requirement to add CMS by creating views dynamically. i have found a solution to load views from database by using VirtualPathProvider class. i have done it successfully and my next problem is we can not write actions for those dynamic views can anyone share their experience how i render my views and their content by using one action.

in simple words just need to create a common action by whom i can render my views (unlimited because of database) from database.

What I have tried:

Thanks for you guys in advance, i need q quick replies.

Posted 5-Feb-18 0:00am

JitendraPandey

Updated 5-Feb-18 6:52am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

David_Wimbley · Answer 1 · 2018-02-05T06:52:00

You need to not think of every page of your CMS as requiring a single action per page and thus a need for 1 generic action...instead you need to break down your CMS into the different types of pages your CMS has and have 1 action per page type.

For example, If you have a CMS that supports creating news articles, personal blogs, and say...displaying a picture gallery, you wouldn't have a single action for every gallery that gets created, rather your CMS would have 3 actions within the CMS's desired controller.

Action 1 - News
Action 2 - Blog
Action 3 - Gallery

Then form those 3 actions, you load the data to their respected models, and pass that model to their respective view accordingly.

If you have built it in such a way where each "page" gets its own unique style and formatting then your going to have to get more complex with customizability from a DB driven perspective but at its simplest form, this is how you can take a CMS with say, 100 pages and turn it into just 3 actions.

I would not suggest 1 generic action unless your CMS only supports 1 type of page (ex: a blog).

If you need to add a new page type...say, a personal file folder UI, then that would be another page type that you'd then add a 4 action to your controller for.