Why doesn’t my Collection Properties get saved in the aspx file properly during design-time?

Platform: ASP.NET| Category: Serialization

Some common mistakes that will cause the designer to choke while persisting collection properties are:

The corresponding collection type cannot have multiple (overloaded) indexers. You should always define a single indexer of the type ‘public SomeType this[object obj]{…}‘. Otherwise the changes will be persisted but the control will not load in the designer. You will see a ‘Ambiguous match found’ error.

If the collection property has the PersistenceMode attribute set to InnerProperty then the property should not include a set method.

Related FAQs

Why doesn't changes made to some of my properties don't get saved in the aspx file during design time?

Why doesn't my properties tagged with the PersistenceMode.InnerProperty attribute get saved in the aspx file?

Is there a method similar to Response.Redirect that will send variables to the destination page other than using a query string or the post method

Where can I get the details on Migration of existing projects using various technologies to ASP.NET

Are there resources online with tips on ASP to ASP.Net conversions?

Couldn't find the FAQs you're looking for?

Please submit your question and answer.

Back to ASP.NET Categories