Your LongListSelector
has a number of items inside. They are added there through data binding by binding the ItemsSource
to items which are a part of Items
collection. This collection can be a List<T>
or more often ObservableCollection<T>
because that way, if properly implemented, the changes in ObservableCollection
will reflect in your LongListSelector
. The T
is the type of your item - for example, a class called Book
. This collection needs to be defined as a part of the DataContext object, which you set on the whole page or a part of page.
Now, as I mentioned, the Items
collection is probably full of items - objects defined to have certain properties. In your case, those properties are LineOne
and LineTwo
, which are probably strings.
You cannot directly bind to items in isolated storage. You first need to load those items into memory. Let's assume you have a list of items serialized to JSON or XML format in your isolated storage, which is one popular way of keeping the list in isolated storage. You need to load them into a collection (deserialize) and then bind to LongListSelector
. It is the right approach, yes.
The yellow image/rectangle/border defined on the left is static, but it can be there, of course. It will simply be rendered there as a part of every item you have in your LongListSelector
and it will not depend on the object which you bind to.
I suggest you read the following articles/questions and answers which may explain the concept of binding to a list easier for you to understand: