Databases
StackOverflow2013
Postsdbo
POBest practices for web application workflow?
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBest practices for web application workflow?
    text
    copied!<p>Note: By workflow i'm not referring to workflow technology, such as Workflow foundation. </p> <p>All too often I find myself being required to design pages that flow through a series of steps. </p> <p>1) Select from a set of options. Submit. 2) Populate a page with results. Make changes. Submit. 3) Do something based on the previous results. Submit. 4) Confirm previous actions. Submit. 5) Goto 1.</p> <p>An ecommerce site with shopping cart would be a textbook example of this.</p> <p>Now, there are any number of ways to deal with this. My question is, what is the recommended way to do it in asp.net? In PHP or ISAPI I would just use standard html controls, get the post data and do stuff with it, each on a different page. </p> <p>ASP.NET seems to be more oriented towards single page solutions. Do your work, postback to yourself, then display your results in the same page.. moving along until the end, using something like a MultiView or UpdatePanels to do the job. But the key being, you don't postback to another page.</p> <p>Now I understand that Microsoft has added cross-page postbacks to .NET in recent versions, but this seemss less baked and kind of cumbersome. It's difficult to work with data that was posted back unless you expose it via properties or something from your previous page.</p> <p>How do you handle the scenario I layed out above? Do you use a multi-view or updatepanel and do it all in one page? Or do you do it in several pages? What is your best practices in this regard? Do you have any specific designs you tend to use? How do you go about structuring the sites workflow?</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload