Passing list collection from page to page

Question

Using wp 8.1 and c#, I need to build a collection on one page1, then use the collection throughout the app for every page including page2, page3, page4, etc.
Can anybody offer advise to consider?
I thank the Lord Jesus for your kind effort and patience with me (Jeremiah 9:23-24 of the Holy Bible).

Answer 1

Is this Silverlight or is it windows store app?
It doesn't matter a great deal.
You have three options.
1)
You can add any old object you like to resources and there's an application scoped set of resource.
In windows store apps I think that'd be app.current.resources and in silverlight it's application.current.resources.
You do:
Application.Current.Resources.Add("somekey", yourlist);
and that adds it to your resources.
App.current... for win store app.
To get a reference back to that thing ( note, it's a reference and therefore the same object).
List<t> mylist =Application.Current.Resources["somekey"] as List<t>;
Obviously, that list can instead be some other sort of collection and <t> is the type of the objects in it.
You can see this approach used in one of my WPF samples:
https://gallery.technet.microsoft.com/Dynamic-XAML-Composed-View-e087f3c1
This shares two observable collections in a similar manner.
It proves they are definitely the same object because you can edit a person and see the changes immediately in the corresponding datagrid row.
2)
You could alternatively send the List<t> using Mvvm Light messenger in an object and subscribe to that object type in the "receiving" pages.  They would have to be in memory and I think option 1 is your best bet.
3)
You could create the collection in one place - like mainpage eg.  Then pass that collection via the constructors of the other pages as you new them up.  I don't really like this approach because it introduces a dependency to all those pages which
means testing etc is harder.   I don't consider it a professional approach if there's an alternative - but it's an approach plenty of professionals advocate so your mileage may vary.
It's not really any simpler than using resources.
Hope that helps.
Recent Technet articles:
Property List Editing ;  
Dynamic XAML