title: Prevent WPF Frame from storing history in the stack
body: <p>This seems like it would be an easy solution, but I'm wasting too much time trying to figure this out.  Perhaps I am designing my application incorrectly (which might be the case), so please help me out if you have a better solution.</p>
  
  <p>I'm designing an enterprise level WPF application that looks a lot like Outlook with a <code>Ribbon</code> instead of a toolbar.  I have a lot of different modules that are loaded into a frame when the user clicks on a <code>RibbonButton</code>.  Keep in mind that his ribbon is shared accross all modules.</p>
  
  <p>So I have a shell with a ribbon and a frame.  When the user clicks on the Ribbon button, it loads the proper module (usercontrol) into the frame.  All is good.  However, if I navigate to another module (by clicking on another RibbonButton), and then click on the original <code>RibbonButton</code>, I now have two instances of the same module open... but only one is shown in the frame... the other module is in the frame's stack.</p>
  
  <p>So my question is, how to I tell the frame to close the usercontrol when I navigate to a different module?  I've tried setting the <code>JournalEntry.KeepAlive="False"</code>, but that still did not work.  Any thoughts?  There is really not much code to post, but I can do so if it will help you.</p>