I am using a custom profile to store values. What I have, compiled great and ran great. Here's just a sample of what I have that works. My web.config has the provider and class inheritance set up. No problems with what already exists.
public class MyProfile : ProfileBase
{
[SettingsAllowAnonymous(false)]
public List<string> SomeItems
{
get { return base["SomeItems"] as List<string>;
set { base["SomeItems"] = value;
}
However, at a much later time I am now adding a new property. It looks exactly the same as above except it's a different property name and different dictionary string (let's say 'SomeItems2'). This guy fails, whereas the original continues to work fine with no pro ...
Go to the complete details ...