Should i worrie?

[Edwin Knoppert]

I read that i should use the viewstate to store properties for a
usercontrol.
But what will happen when i have 2 or more instances of this usercontrol on
the same webpage?

Is the ViewState able to make unique instances for me, i don't think so..

I'm looking for the "how it should" way..

[Martin Gregersen]

Maybe if you use the "this" (C#) or "me" (vb) keyword? Then I would asume that it would behave(?)...

Martin Gregersen
WebShine A/S
gr*******@webshine.dk
"Edwin Knoppert" <ne**@hellobasic.comwrote in message news:45***********************@text.nova.planet.nl ...
I read that i should use the viewstate to store properties for a
usercontrol.
But what will happen when i have 2 or more instances of this usercontrol on
the same webpage?

Is the ViewState able to make unique instances for me, i don't think so..

I'm looking for the "how it should" way..

[Edwin Knoppert]

Indeed!

i just tested two control instances and they remain having unique values.
The example in the help is ok:

public String Text
{
get
{
object o = ViewState["text"];
return (o == null)? String.Empty : (string)o;
}

set
{
ViewState["Text"] = value;
}
}

"Martin Gregersen" <gr*******@webshine.dkschreef in bericht
news:eX**************@TK2MSFTNGP03.phx.gbl...
Maybe if you use the "this" (C#) or "me" (vb) keyword? Then I would asume
that it would behave(?)...

Martin Gregersen
WebShine A/S
gr*******@webshine.dk
"Edwin Knoppert" <ne**@hellobasic.comwrote in message
news:45***********************@text.nova.planet.nl ...
I read that i should use the viewstate to store properties for a
usercontrol.
But what will happen when i have 2 or more instances of this usercontrol on
the same webpage?

Is the ViewState able to make unique instances for me, i don't think so..

I'm looking for the "how it should" way..

[Karl Seguin [MVP]]

Ya. It's pretty smart. Always appends the control's id to the property. You
can easily see this by enabling page tracing.

Also, if you write your own custom server control, if you implement
INamingContainer (no methods are required), it'll take care of it for you
too.

Karl

--
http://www.openmymind.net/
http://www.fuelindustries.com/
"Edwin Knoppert" <ne**@hellobasic.comwrote in message
news:45***********************@text.nova.planet.nl ...

Indeed!

i just tested two control instances and they remain having unique values.
The example in the help is ok:

public String Text
{
get
{
object o = ViewState["text"];
return (o == null)? String.Empty : (string)o;
}

set
{
ViewState["Text"] = value;
}
}

"Martin Gregersen" <gr*******@webshine.dkschreef in bericht
news:eX**************@TK2MSFTNGP03.phx.gbl...
Maybe if you use the "this" (C#) or "me" (vb) keyword? Then I would asume
that it would behave(?)...

Martin Gregersen
WebShine A/S
gr*******@webshine.dk
"Edwin Knoppert" <ne**@hellobasic.comwrote in message
news:45***********************@text.nova.planet.nl ...
I read that i should use the viewstate to store properties for a
usercontrol.
But what will happen when i have 2 or more instances of this usercontrol
on
the same webpage?

Is the ViewState able to make unique instances for me, i don't think so..

I'm looking for the "how it should" way..

[Edwin Knoppert]

Ya. It's pretty smart. Always appends the control's id to the property.
Huh?
I just stated that the viewstate values remain unique by itself.
Iow, no need to add unique id's manually.
Or did i misunderstood your post?

The code i use below should imo be sufficient.

Please correct me if i'm wrong.

Thanks,

"Karl Seguin [MVP]" <karl REMOVE @ REMOVE openmymind REMOVEMETOO . ANDME
netschreef in bericht news:eg**************@TK2MSFTNGP02.phx.gbl...

Ya. It's pretty smart. Always appends the control's id to the property.
You can easily see this by enabling page tracing.

Also, if you write your own custom server control, if you implement
INamingContainer (no methods are required), it'll take care of it for you
too.

Karl

--
http://www.openmymind.net/
http://www.fuelindustries.com/
"Edwin Knoppert" <ne**@hellobasic.comwrote in message
news:45***********************@text.nova.planet.nl ...

>Indeed!

i just tested two control instances and they remain having unique values.
The example in the help is ok:

public String Text
{
get
{
object o = ViewState["text"];
return (o == null)? String.Empty : (string)o;
}

set
{
ViewState["Text"] = value;
}
}

"Martin Gregersen" <gr*******@webshine.dkschreef in bericht
news:eX**************@TK2MSFTNGP03.phx.gbl...
Maybe if you use the "this" (C#) or "me" (vb) keyword? Then I would asume
that it would behave(?)...

Martin Gregersen
WebShine A/S
gr*******@webshine.dk
"Edwin Knoppert" <ne**@hellobasic.comwrote in message
news:45***********************@text.nova.planet.n l...
I read that i should use the viewstate to store properties for a
usercontrol.
But what will happen when i have 2 or more instances of this usercontrol
on
the same webpage?

Is the ViewState able to make unique instances for me, i don't think so..

I'm looking for the "how it should" way..

[Karl Seguin [MVP]]

That's all I was saying...ASP.NET is smart, it takes care of it for you :)

Karl

--
http://www.openmymind.net/
http://www.fuelindustries.com/
"Edwin Knoppert" <ne**@hellobasic.comwrote in message
news:45**********************@text.nova.planet.nl. ..

>Ya. It's pretty smart. Always appends the control's id to the property.

Huh?
I just stated that the viewstate values remain unique by itself.
Iow, no need to add unique id's manually.
Or did i misunderstood your post?

The code i use below should imo be sufficient.

Please correct me if i'm wrong.

Thanks,

"Karl Seguin [MVP]" <karl REMOVE @ REMOVE openmymind REMOVEMETOO . ANDME
netschreef in bericht news:eg**************@TK2MSFTNGP02.phx.gbl...

>Ya. It's pretty smart. Always appends the control's id to the property.
You can easily see this by enabling page tracing.

Also, if you write your own custom server control, if you implement
INamingContainer (no methods are required), it'll take care of it for you
too.

Karl

--
http://www.openmymind.net/
http://www.fuelindustries.com/
"Edwin Knoppert" <ne**@hellobasic.comwrote in message
news:45***********************@text.nova.planet.n l...

>>Indeed!

i just tested two control instances and they remain having unique
values.
The example in the help is ok:

public String Text
{
get
{
object o = ViewState["text"];
return (o == null)? String.Empty : (string)o;
}

set
{
ViewState["Text"] = value;
}
}

"Martin Gregersen" <gr*******@webshine.dkschreef in bericht
news:eX**************@TK2MSFTNGP03.phx.gbl...
Maybe if you use the "this" (C#) or "me" (vb) keyword? Then I would
asume that it would behave(?)...

Martin Gregersen
WebShine A/S
gr*******@webshine.dk
"Edwin Knoppert" <ne**@hellobasic.comwrote in message
news:45***********************@text.nova.planet. nl...
I read that i should use the viewstate to store properties for a
usercontrol.
But what will happen when i have 2 or more instances of this usercontrol
on
the same webpage?

Is the ViewState able to make unique instances for me, i don't think
so..

I'm looking for the "how it should" way..

[Edwin Knoppert]

Thank you :)

"Karl Seguin [MVP]" <karl REMOVE @ REMOVE openmymind REMOVEMETOO . ANDME
netschreef in bericht news:%2****************@TK2MSFTNGP04.phx.gbl...

That's all I was saying...ASP.NET is smart, it takes care of it for you :)

Karl

--
http://www.openmymind.net/
http://www.fuelindustries.com/
"Edwin Knoppert" <ne**@hellobasic.comwrote in message
news:45**********************@text.nova.planet.nl. ..

>>Ya. It's pretty smart. Always appends the control's id to the property.

Huh?
I just stated that the viewstate values remain unique by itself.
Iow, no need to add unique id's manually.
Or did i misunderstood your post?

The code i use below should imo be sufficient.

Please correct me if i'm wrong.

Thanks,

"Karl Seguin [MVP]" <karl REMOVE @ REMOVE openmymind REMOVEMETOO . ANDME
netschreef in bericht news:eg**************@TK2MSFTNGP02.phx.gbl...

>>Ya. It's pretty smart. Always appends the control's id to the property.
You can easily see this by enabling page tracing.

Also, if you write your own custom server control, if you implement
INamingContainer (no methods are required), it'll take care of it for
you too.

Karl

--
http://www.openmymind.net/
http://www.fuelindustries.com/
"Edwin Knoppert" <ne**@hellobasic.comwrote in message
news:45***********************@text.nova.planet. nl...
Indeed!

i just tested two control instances and they remain having unique
values.
The example in the help is ok:

public String Text
{
get
{
object o = ViewState["text"];
return (o == null)? String.Empty : (string)o;
}

set
{
ViewState["Text"] = value;
}
}

"Martin Gregersen" <gr*******@webshine.dkschreef in bericht
news:eX**************@TK2MSFTNGP03.phx.gbl...
Maybe if you use the "this" (C#) or "me" (vb) keyword? Then I would
asume that it would behave(?)...

Martin Gregersen
WebShine A/S
gr*******@webshine.dk
"Edwin Knoppert" <ne**@hellobasic.comwrote in message
news:45***********************@text.nova.planet .nl...
I read that i should use the viewstate to store properties for a
usercontrol.
But what will happen when i have 2 or more instances of this
usercontrol on
the same webpage?

Is the ViewState able to make unique instances for me, i don't think
so..

I'm looking for the "how it should" way..