Designing Modular Webmasters Using .Net 2.0 Wizard Control

We have about 10 applications that basically do the same thing, everything is written using Wizard Control for .Net 2.0. The stream that they follow is pretty simple:

1. User selects option from a drop downs.
2. Next page has more options more narrowed.
3. User sees confirmation page.
4. Report is generated.

Some of these applications have optional pages, for example, allowing the user to upload custom images for the report and allowing the user to select specific rows of data.

I am trying to combine these applications, but I am not sure if I am approaching this in the right way. My first slant is to create configuration tables in SQL to control the displayed menus. So, for example, can be a table WizardId, Name, Themeetc., is also a table and another table of steps to tie everything together.

Is there an easier way to approach this that I'm just missing?

+3
source share
1 answer

We have been discussing this issue recently, and I came up with two options that seem valid but have different uses. One way to do this, similar to what you described, is to create the following:

  • The table that contains the wizard information
  • A table listing the types of questions asked in each wizard.
  • A table for storing user input for each question

, , , ( , , , ..) , .

, , - . , , .

, . , , , .

0

Source: https://habr.com/ru/post/1699305/


All Articles