title: Guidelines for using ASP.NET Panels/multiview vs separate pages
body: <p>It's often necessary to create a UI to walk a user through a multi-step process. There is two common designs that one could use. One option is to make each step a separate page. Another option is to use either asp:panels or the multiview control and keep all the code within one asp.net page.</p>
  
  <p>Whenever I use the seperate page approach, I find that data sharing between pages is kludgy. </p>
  
  <p>Whenever I use the multiview approach, I find that the code-behind logic loses cohesion. It's dealing with too many items at once and gets hard to follow.</p>
  
  <p>What criteria do you use when deciding which approach to use?</p>
  
  <p>Is there other design patterns that could help with the limitations I find in the existing options?</p>