title: Windows form/WPF too large, how can i split it up?
body: <p>I'm about to create WPF application. So far at uni the only way we have ever done GUIs is to have one main window with one code-behind file for handling its button clicks etc.. </p>
  
  <p>My issue is that as the application grows, the GUI grows, and the size of the code behind file can get really out of hand!</p>
  
  <p>I have identified about 15 main use cases for my system (example: enter details, view details, etc...). I am creating a main window (size: 480x320) that consists of 15 seperate screens (one for each use case). This could be achieved with a centered and stretched TabControl, with 15 TabItem's. Or more likely it could just be a bunch of layered containers, one on top of the other (only one visible at a time). </p>
  
  <p>The point is, with 15 seperate screens, my code-behind file will become enormous (not to mention the xaml file!): Juggling between states - making 14 collapsed/hidden and making one visible, Handling the controls for 15 different screens.</p>
  
  <p>Is there a way to having 15 seperate forms, each with its own code-behind file, instead of 15 TabItems on the one form, and then having one main engine creating and scrapping them as needed? Ofcourse, it should appear as though it is one form, not 15 pop ups. </p>
  
  <p>How do i deal with this? How would you deal with the issue of xaml and code-behind files that are thousands of lines long?</p>