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.
New to silverlight. Traditionally if I were to design a wizard-like process where a user had to go through 3 or 4 steps, I’d have each step as a separate aspx page. Using silverlight, would you do it all in one component, or would you have 3 separate pages each with a different silverlight component? What kind of advantages/disadvantages are there for either approach?
A wizard typically needs to maintain state between screens, which would be much easier to do on a single page instead of multiple pages. You also have the benefit of initializing a SL control once instead of multiple times.
The disadvantage to loading the whole wizard on one page is that one SL control has the potential to be bigger than several smaller controls, depending on how you package it all up. This means a longer initialization time. Also, I would worry about the user using the back and forward buttons in the browser to navigate the wizard. I don’t know if you can intercept those clicks from Silverlight and just navigate the SL control screens back or forward, or if you even want to do so.
If the wizard is only a few screens I would imagine the pros of using it on one page outweigh the cons.