Note: I do not refer to workflow technologies such as workflow foundations from workflow.
Everyone often thinks that pages that come through a series of different steps need to be designed. <
1) Choose from a set of options. . 2) Populate a page with results, make changes. Submit 3) Submit something on the basis of past results. 4) Confirm previous actions Submit. 5) goto 1. An ecommerce site with shopping cart will be a textbook example of this.
Now, there are several ways to deal with this. My question is, what is the recommended way to do this in ASP.NET? In PHP or ISAPI, I use standard HTML control, get post data and do stuff with it, on each separate page
ASP.Net seems more oriented towards one page solution. Do your job, postback yourself, then show your results in a single page. To work, proceed to the end by using something like multivis or update panels. But being the key, you do not post on any other page.
Now I understand that in Microsoft recent versions Cross-page postbacks have been added to the net, but it seems less baked and kind of cumbersome. It is difficult to work with the data that was posted back until you expose it from your previous page through properties or some things.
How do I keep the scenario above? Do you use a multi-view or updatepanel and do all this in one page? Or do you do it in many pages? What are your best practices in this regard? Do you have any specific design that you use? How can you go about structuring site workflow? There are several ways (besides multi-view):
2, You can save your temporary data in the temporary table of the database, Page, then they refer to the temporary data ID in the database. (Query string)
3, you can also save your temporary data as an object in your session, so you can refer to all your page sessions in the "work flow", then depending on it Manipulate it.
After all, they are all professionals and Opposition, it mainly depends on the complexity of your project's needs.
Comments
Post a Comment