Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am using asp.net mvc and in my web app users will be prompted in multiple steps to acquire information or to cancel (or go back) the action mid way. Can someone recommend an implementation way to tackle this.
Should I use a 1 action method per prompt ?
Or should I do every prompt in javascript on the client side ?
Or any other approaches will be welcomed .
Based on the details from your comment, it seems like the best solution would be to simply break everything up into separate Actions as you mentioned in your original question.
The reason behind this is that you have ‘a lot’ going on at each step, you are likely to want more than just client-side validation at each step, and you may want to prepare for the situation where someone’s browser fails (or they just close it for some reason) at some point between the beginning and end of the process – you may want them to be able to pick up where they left off.
It would likely be easier to manage all of the steps on your end and keep things feeling ‘solid’ as your users move through the process if you keep everything as separate actions.