Help with using a custom collection as a property for a TextBox derrived control.

[Chris Crowe [MVP]]

Hi

I am creating a new TextBox control but I am having problems when I am
trying to add my own collection to the control and persisting the values to
the asp.net web page.

This is my code for the collection property

[PersistenceMode(PersistenceMode.InnerProperty)]
public LookupEditControlColumns ListColumns

This is correctly persisting the data as follows:

<cc1:lookupeditcontrol id="LookupEditControl2" runat="server"
PopupWindow="True" LookupURL="search.aspx?ctrl=name&amp;v=">
<ListColumns>
<cc1:LookupEditControlColumn Width="100%"></cc1:LookupEditControlColumn>
</ListColumns>
</cc1:lookupeditcontrol>

But when you open the .aspx page I get the following problem.

The text property of the control contains the following

<ListColumns>
<cc1:LookupEditControlColumn
Width="100%"></cc1:LookupEditControlColumn>
</ListColumns>

and my collection is empty.

How do I handle this situation?

Is there anything else I must do when I want to persist my custom collection
properties?

--
Cheers

Chris

Chris Crowe [IIS MVP]

[Shaun Wilde]

I have a similar issue as you and I found this article that seems to have a
good answer that I am going to employ myself - I've been using a similar
trick (i.e. calling OnComponentChanged - have a search for
notifyDesignerOfChange in this group) with a simple string property but the
collection property was causing issues (i.e. sometimes saving and sometimes
not)

"Chris Crowe [MVP]" wrote:

> Hi
>
> I am creating a new TextBox control but I am having problems when I am
> trying to add my own collection to the control and persisting the values to
> the asp.net web page.
>
> This is my code for the collection property
>
> [PersistenceMode(PersistenceMode.InnerProperty)]
> public LookupEditControlColumns ListColumns
>
> This is correctly persisting the data as follows:
>
> <cc1:lookupeditcontrol id="LookupEditControl2" runat="server"
> PopupWindow="True" LookupURL="search.aspx?ctrl=name&v=">
> <ListColumns>
> <cc1:LookupEditControlColumn Width="100%"></cc1:LookupEditControlColumn>
> </ListColumns>
> </cc1:lookupeditcontrol>
>
> But when you open the .aspx page I get the following problem.
>
> The text property of the control contains the following
>
> <ListColumns>
> <cc1:LookupEditControlColumn
> Width="100%"></cc1:LookupEditControlColumn>
> </ListColumns>
>
> and my collection is empty.
>
> How do I handle this situation?
>
> Is there anything else I must do when I want to persist my custom collection
> properties?
>
> --
> Cheers
>
> Chris
>
> Chris Crowe [IIS MVP]
>
>
>

[Shaun Wilde]

oops forgot to put link in :) [url]http://weblogs.asp.net/ngur/articles/144770.aspx[/url]

"Shaun Wilde" wrote:

> I have a similar issue as you and I found this article that seems to have a
> good answer that I am going to employ myself - I've been using a similar
> trick (i.e. calling OnComponentChanged - have a search for
> notifyDesignerOfChange in this group) with a simple string property but the
> collection property was causing issues (i.e. sometimes saving and sometimes
> not)
>
> "Chris Crowe [MVP]" wrote:
>

> > Hi
> >
> > I am creating a new TextBox control but I am having problems when I am
> > trying to add my own collection to the control and persisting the values to
> > the asp.net web page.
> >
> > This is my code for the collection property
> >
> > [PersistenceMode(PersistenceMode.InnerProperty)]
> > public LookupEditControlColumns ListColumns
> >
> > This is correctly persisting the data as follows:
> >
> > <cc1:lookupeditcontrol id="LookupEditControl2" runat="server"
> > PopupWindow="True" LookupURL="search.aspx?ctrl=name&v=">
> > <ListColumns>
> > <cc1:LookupEditControlColumn Width="100%"></cc1:LookupEditControlColumn>
> > </ListColumns>
> > </cc1:lookupeditcontrol>
> >
> > But when you open the .aspx page I get the following problem.
> >
> > The text property of the control contains the following
> >
> > <ListColumns>
> > <cc1:LookupEditControlColumn
> > Width="100%"></cc1:LookupEditControlColumn>
> > </ListColumns>
> >
> > and my collection is empty.
> >
> > How do I handle this situation?
> >
> > Is there anything else I must do when I want to persist my custom collection
> > properties?
> >
> > --
> > Cheers
> >
> > Chris
> >
> > Chris Crowe [IIS MVP]
> >
> >
> >

[Chris Crowe [MVP]]

Thanks Shaun

I will into that solution - at this time I basically wet back to using a
WebControl and then adding the code to make it back to a TextBox which is
working for me.

Cheers

Chris

Chris Crowe [IIS MVP]
[url]http://blog.crowe.co.nz[/url]


"Shaun Wilde" <shaun_wilde@nospam.nospam> wrote in message
news:60C7E19D-4DE7-4380-97AF-288DACFE0160@microsoft.com...

>I have a similar issue as you and I found this article that seems to have a
> good answer that I am going to employ myself - I've been using a similar
> trick (i.e. calling OnComponentChanged - have a search for
> notifyDesignerOfChange in this group) with a simple string property but
> the
> collection property was causing issues (i.e. sometimes saving and
> sometimes
> not)
>
> "Chris Crowe [MVP]" wrote:
>

>> Hi
>>
>> I am creating a new TextBox control but I am having problems when I am
>> trying to add my own collection to the control and persisting the values
>> to
>> the asp.net web page.
>>
>> This is my code for the collection property
>>
>> [PersistenceMode(PersistenceMode.InnerProperty)]
>> public LookupEditControlColumns ListColumns
>>
>> This is correctly persisting the data as follows:
>>
>> <cc1:lookupeditcontrol id="LookupEditControl2" runat="server"
>> PopupWindow="True" LookupURL="search.aspx?ctrl=name&v=">
>> <ListColumns>
>> <cc1:LookupEditControlColumn Width="100%"></cc1:LookupEditControlColumn>
>> </ListColumns>
>> </cc1:lookupeditcontrol>
>>
>> But when you open the .aspx page I get the following problem.
>>
>> The text property of the control contains the following
>>
>> <ListColumns>
>> <cc1:LookupEditControlColumn
>> Width="100%"></cc1:LookupEditControlColumn>
>> </ListColumns>
>>
>> and my collection is empty.
>>
>> How do I handle this situation?
>>
>> Is there anything else I must do when I want to persist my custom
>> collection
>> properties?
>>
>> --
>> Cheers
>>
>> Chris
>>
>> Chris Crowe [IIS MVP]
>>
>>
>>