NavigationCacheMode is readonly problem ...

Question

Hello everyone. First post - please be gentle ;-)
I have a problem with the 'back' browsing for a particular page and I want to turn off cacheing.
I'm trying to do it like this:
public partial class MainPage : PhoneApplicationPage
// Constructor
public MainPage()
InitializeComponent();
NavigationCacheMode = System.Windows.Navigation.NavigationCacheMode.Disabled;
Blah ...
Unfortunately the property is internal to Assembly Microsoft.Phone.dll, v2.0.50727; so I can't set it. The declaration is this: 
public NavigationCacheMode NavigationCacheMode { get; internal
set; }
So the compiler tells me:
"Error
1 Property or indexer 'System.Windows.Controls.Page.NavigationCacheMode' cannot be assigned to -- it is read only"
I tried setting it in xaml too in case there was some magic involved but to no avail.
So can anyone tell me how to prevent the NavigationService from cacheing my page? I'd expected at least some sort of Reload method but can't find one.
Any help much appreciated.
Keith

Answer 1

Hi Jonathan, thanks for the reply. I found a workaround. (By improving my UI design!)
Your link was useful but for another reason. :-)
I have a page that is databound to an object in a hierarchy and shows the object's children. You can click on a child and the child becomes the datacontext for the next page ... Essentially I'm navigating down a tree-structure and relying on the 'back'
button to get me back up.
The problem was that some object properties have a one-way databinding to the view, so the view can modify it's content without affecting the underlying view-model. Navigating forwards is obviously fine but I found that navigating back up displays cached
copies of the 'parent' page that may have user-input in some controls rather than 'clean' values from the view-model.
If anyone is interested I think I saw this behaviour because when I returned to the cached page, I was setting the datacontext to the same value it already had, and the event pattern for this scenario says to do nothing. I expect that if I'd actually changed
the view-model that a cached page was bound to then the databindings on the cached page would receive 'data changed' notifications and therefore all would be well. (Even though the page is cached and therefore not visible).
Still, it seems a bit odd that we are forced to cache entire pages rather than just the page urls - the most obvious problems being (As Pieter discovered) what if pages consume a lot of memory?
Thanks again,
Keith