Once again where is the cached info

[Lloyd Sheen]

Ok what I am doing is simple (I thought).

I have a linq to sql set of classes in my project. I am attempting to use
one of the classes as datasource. No big problem except that I need a
readonly property that I create in the class manually for binding purposes.

I create the property and can use it anywhere (and I know that if I change
database descriptions I will have to redo this part). I then create the
datasource. When I look at the properties in the datasource my new property
is not there.

To "prove" the part about caching I created a brand new project. Added same
readonly property (before I did any datasources). Add the datasource as the
object and voila the property is there. If I delete the datasource and add
a new readonly for testing purposes there is no way I can make VS see this
property for the datasource. It can be used in code.

So what is going on? I would just like to get rid of whatever is causing
the caching of info that need to be refreshed.

Lloyd Sheen