473,326 Members | 2,013 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,326 software developers and data experts.

User control remember state across pages without session

Is there a way to get a user control to remember its state across pages? I
have a standard page layout I use with a header and footer as user controls.
Each page uses the same layout by means of copy paste (I hear this will
improve in ASP.Net 2 via master pages).

When I navigate from one page to the next the header and footer user
controls lose their state because they are effectively different instances
of the user control.

Is there any way I can make the state of the user control exist between
pages?

Preferably without the use of hand coding the storing of data in the session
or passing parameters to the user control on each page that includes it. Is
there a way of making the user control state "global"?

Thanks!

--
McGeeky
http://mcgeeky.blogspot.com

Nov 19 '05 #1
9 5278
KMA
should the state of the UC be the same for all clients?

"McGeeky" <an**@anon.com> wrote in message
news:uh**************@TK2MSFTNGP09.phx.gbl...
Is there a way to get a user control to remember its state across pages? I
have a standard page layout I use with a header and footer as user controls. Each page uses the same layout by means of copy paste (I hear this will
improve in ASP.Net 2 via master pages).

When I navigate from one page to the next the header and footer user
controls lose their state because they are effectively different instances
of the user control.

Is there any way I can make the state of the user control exist between
pages?

Preferably without the use of hand coding the storing of data in the session or passing parameters to the user control on each page that includes it. Is there a way of making the user control state "global"?

Thanks!

--
McGeeky
http://mcgeeky.blogspot.com

Nov 19 '05 #2
No. It could be different for each client

--
McGeeky
http://mcgeeky.blogspot.com
"KMA" <km*@chum.com> wrote in message news:dj**********@atlas.ip-plus.net...
should the state of the UC be the same for all clients?

"McGeeky" <an**@anon.com> wrote in message
news:uh**************@TK2MSFTNGP09.phx.gbl...
Is there a way to get a user control to remember its state across pages?
I
have a standard page layout I use with a header and footer as user

controls.
Each page uses the same layout by means of copy paste (I hear this will
improve in ASP.Net 2 via master pages).

When I navigate from one page to the next the header and footer user
controls lose their state because they are effectively different
instances
of the user control.

Is there any way I can make the state of the user control exist between
pages?

Preferably without the use of hand coding the storing of data in the

session
or passing parameters to the user control on each page that includes it.

Is
there a way of making the user control state "global"?

Thanks!

--
McGeeky
http://mcgeeky.blogspot.com


Nov 19 '05 #3
KMA
Well, the control state isn't "global", is it. It depends on the client, or
session of that client to be precise. What's your objection to using session
state to store the state of the session?
"McGeeky" <an**@anon.com> wrote in message
news:Oz**************@TK2MSFTNGP09.phx.gbl...
No. It could be different for each client

--
McGeeky
http://mcgeeky.blogspot.com
"KMA" <km*@chum.com> wrote in message

news:dj**********@atlas.ip-plus.net...
should the state of the UC be the same for all clients?

"McGeeky" <an**@anon.com> wrote in message
news:uh**************@TK2MSFTNGP09.phx.gbl...
Is there a way to get a user control to remember its state across pages? I
have a standard page layout I use with a header and footer as user

controls.
Each page uses the same layout by means of copy paste (I hear this will
improve in ASP.Net 2 via master pages).

When I navigate from one page to the next the header and footer user
controls lose their state because they are effectively different
instances
of the user control.

Is there any way I can make the state of the user control exist between
pages?

Preferably without the use of hand coding the storing of data in the

session
or passing parameters to the user control on each page that includes
it. Is
there a way of making the user control state "global"?

Thanks!

--
McGeeky
http://mcgeeky.blogspot.com



Nov 19 '05 #4
My preference is that all state should be passed to each page as URL
parameters to make testing and problem determination much easier.

I thought that there would be some way for a user control's viewstate to
persist between pages without having to use the session.

--
McGeeky
http://mcgeeky.blogspot.com
"KMA" <km*@chum.com> wrote in message news:dj**********@atlas.ip-plus.net...
Well, the control state isn't "global", is it. It depends on the client,
or
session of that client to be precise. What's your objection to using
session
state to store the state of the session?
"McGeeky" <an**@anon.com> wrote in message
news:Oz**************@TK2MSFTNGP09.phx.gbl...
No. It could be different for each client

--
McGeeky
http://mcgeeky.blogspot.com
"KMA" <km*@chum.com> wrote in message

news:dj**********@atlas.ip-plus.net...
> should the state of the UC be the same for all clients?
>
> "McGeeky" <an**@anon.com> wrote in message
> news:uh**************@TK2MSFTNGP09.phx.gbl...
>> Is there a way to get a user control to remember its state across pages? >> I
>> have a standard page layout I use with a header and footer as user
> controls.
>> Each page uses the same layout by means of copy paste (I hear this
>> will
>> improve in ASP.Net 2 via master pages).
>>
>> When I navigate from one page to the next the header and footer user
>> controls lose their state because they are effectively different
>> instances
>> of the user control.
>>
>> Is there any way I can make the state of the user control exist
>> between
>> pages?
>>
>> Preferably without the use of hand coding the storing of data in the
> session
>> or passing parameters to the user control on each page that includes it. > Is
>> there a way of making the user control state "global"?
>>
>> Thanks!
>>
>> --
>> McGeeky
>> http://mcgeeky.blogspot.com
>>
>>
>>
>
>



Nov 19 '05 #5
I should clarify:

I thought that there would be some **automatic** way for a user control's
viewstate to persist between pages without having to use the session.

Thanks

--
McGeeky
http://mcgeeky.blogspot.com
"McGeeky" <an**@anon.com> wrote in message
news:O3****************@tk2msftngp13.phx.gbl...
My preference is that all state should be passed to each page as URL
parameters to make testing and problem determination much easier.

I thought that there would be some way for a user control's viewstate to
persist between pages without having to use the session.

--
McGeeky
http://mcgeeky.blogspot.com
"KMA" <km*@chum.com> wrote in message
news:dj**********@atlas.ip-plus.net...
Well, the control state isn't "global", is it. It depends on the client,
or
session of that client to be precise. What's your objection to using
session
state to store the state of the session?
"McGeeky" <an**@anon.com> wrote in message
news:Oz**************@TK2MSFTNGP09.phx.gbl...
No. It could be different for each client

--
McGeeky
http://mcgeeky.blogspot.com
"KMA" <km*@chum.com> wrote in message

news:dj**********@atlas.ip-plus.net...
> should the state of the UC be the same for all clients?
>
> "McGeeky" <an**@anon.com> wrote in message
> news:uh**************@TK2MSFTNGP09.phx.gbl...
>> Is there a way to get a user control to remember its state across

pages?
>> I
>> have a standard page layout I use with a header and footer as user
> controls.
>> Each page uses the same layout by means of copy paste (I hear this
>> will
>> improve in ASP.Net 2 via master pages).
>>
>> When I navigate from one page to the next the header and footer user
>> controls lose their state because they are effectively different
>> instances
>> of the user control.
>>
>> Is there any way I can make the state of the user control exist
>> between
>> pages?
>>
>> Preferably without the use of hand coding the storing of data in the
> session
>> or passing parameters to the user control on each page that includes

it.
> Is
>> there a way of making the user control state "global"?
>>
>> Thanks!
>>
>> --
>> McGeeky
>> http://mcgeeky.blogspot.com
>>
>>
>>
>
>



Nov 19 '05 #6
HTTP is stateless. An HTTP Request is received by the web server. It hands
it off the the ASP.Net application. The application identifies the handler
for that Request (a Page class). The Page class is instantiated and handles
the Request. It sends a Response to the client. Then it goes out of scope,
off into NothingLand. The next Request comes for a Page. The same thing
happens again.

Now, as HTTP is stateless, ASP.Net includes some tricks for persisting state
across Page Requests. One is the PostBack. When the PostBack is received, it
contains the values in the Page, which are used to re-build the Page class
on the server in the state it was on the client. Without it, the Page form
would be completely empty of values, as HTTP is stateless. Another is
ViewState. ViewState uses a hidden form field which is inserted into the
Page when the Response is sent to the browser. It contains the current state
of all the form elements in the Page. When the Page Posts back, the
ViewState is read, and the new Page instance is re-populated with the saved
state of the Page coming from the POST Request.

Note that this enables ONE PAGE class to remember the state IT was in prior
to a PostBack. So, how do you persist data across multiple pages? After all,
HTTP IS STATELESS (I'm going to keep repeating this so that you will get it
drummed into your head - it is VERY important). Well, HTML has a mechanism
for remembering a few things. It's called Cookies. So, when the first
Request for a Page comes from any client, the Session Collection has a new
member added to it, with a unique ID, a Guid, that identifies the client
that sent the Request. This Guid is sent back to the client in the
Response.Cookies collection, as a Session Cookie (it is not saved on the
client, except during the current Session). Every time the browser makes a
Request, it sends its Cookies in the Request header. The server reads the
Session Cookie, and uses the Session object for that client during that
Request/Response.

So, are there any other ways to save the state of a User Control across
multiple page requests? Sure, but they all involve one thing: The client
must be uniquely identified on the server, so that the Page handling the
Request, which remembers nothing about any previous Requests (because HTTP
IS STATELESS), can identify what client data to fetch for that Page. How to
do that? Well, a Cookie comes to mind. You could create a Guid on the
server, and pass it to the client in the Response.Cookies Collection, and
read it every time a new Request comes back. You would have to store both
the Cookie Guid, and the User Control data somewhere. Now, you obviously
don't want to store it in memory, or you would probably use Session. You
could store it in a database, though, for example. Of course, as HTTP IS
STATELESS, and the server has no way to know when the client user has lost
interest and navigated somewhere else, you would have to include some sort
of Timeout process to remove the data from the database after a specified
interval with no Requests.

This is, of course, how Session works. So you don't have to.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Ambiguity has a certain quality to it.

"McGeeky" <an**@anon.com> wrote in message
news:en*************@TK2MSFTNGP15.phx.gbl...
I should clarify:

I thought that there would be some **automatic** way for a user control's
viewstate to persist between pages without having to use the session.

Thanks

--
McGeeky
http://mcgeeky.blogspot.com
"McGeeky" <an**@anon.com> wrote in message
news:O3****************@tk2msftngp13.phx.gbl...
My preference is that all state should be passed to each page as URL
parameters to make testing and problem determination much easier.

I thought that there would be some way for a user control's viewstate to
persist between pages without having to use the session.

--
McGeeky
http://mcgeeky.blogspot.com
"KMA" <km*@chum.com> wrote in message
news:dj**********@atlas.ip-plus.net...
Well, the control state isn't "global", is it. It depends on the client,
or
session of that client to be precise. What's your objection to using
session
state to store the state of the session?
"McGeeky" <an**@anon.com> wrote in message
news:Oz**************@TK2MSFTNGP09.phx.gbl...
No. It could be different for each client

--
McGeeky
http://mcgeeky.blogspot.com
"KMA" <km*@chum.com> wrote in message
news:dj**********@atlas.ip-plus.net...
> should the state of the UC be the same for all clients?
>
> "McGeeky" <an**@anon.com> wrote in message
> news:uh**************@TK2MSFTNGP09.phx.gbl...
>> Is there a way to get a user control to remember its state across
pages?
>> I
>> have a standard page layout I use with a header and footer as user
> controls.
>> Each page uses the same layout by means of copy paste (I hear this
>> will
>> improve in ASP.Net 2 via master pages).
>>
>> When I navigate from one page to the next the header and footer user
>> controls lose their state because they are effectively different
>> instances
>> of the user control.
>>
>> Is there any way I can make the state of the user control exist
>> between
>> pages?
>>
>> Preferably without the use of hand coding the storing of data in the
> session
>> or passing parameters to the user control on each page that includes
it.
> Is
>> there a way of making the user control state "global"?
>>
>> Thanks!
>>
>> --
>> McGeeky
>> http://mcgeeky.blogspot.com
>>
>>
>>
>
>



Nov 19 '05 #7
you should use session, but put the code in the header and footer so the
pages need no knowledge of it. this is called encapsulation, a main design
feature of oo languages.

-- bruce (sqlwork.com)

"McGeeky" <an**@anon.com> wrote in message
news:uh**************@TK2MSFTNGP09.phx.gbl...
Is there a way to get a user control to remember its state across pages? I
have a standard page layout I use with a header and footer as user
controls. Each page uses the same layout by means of copy paste (I hear
this will improve in ASP.Net 2 via master pages).

When I navigate from one page to the next the header and footer user
controls lose their state because they are effectively different instances
of the user control.

Is there any way I can make the state of the user control exist between
pages?

Preferably without the use of hand coding the storing of data in the
session or passing parameters to the user control on each page that
includes it. Is there a way of making the user control state "global"?

Thanks!

--
McGeeky
http://mcgeeky.blogspot.com

Nov 19 '05 #8
KMA
It would eat into bandwidth a bit. And by the time you've specified what
should and shouldn't be included you could have just coded the storage in
Session, which , after all, is the appropriate place.

You should have seen what things were like before Session.
"McGeeky" <an**@anon.com> wrote in message
news:OI**************@TK2MSFTNGP15.phx.gbl...
So, no, a user control cannot maintain state across pages without using the session.

Its a shame Microsoft don't extend viewstate beyond a single page because it would be very useful.

--
McGeeky
http://mcgeeky.blogspot.com
"Kevin Spencer" <ke***@DIESPAMMERSDIEtakempis.com> wrote in message
news:e8**************@TK2MSFTNGP15.phx.gbl...
HTTP is stateless. An HTTP Request is received by the web server. It hands
it off the the ASP.Net application. The application identifies the handler for that Request (a Page class). The Page class is instantiated and handles
the Request. It sends a Response to the client. Then it goes out of scope, off into NothingLand. The next Request comes for a Page. The same thing
happens again.

Now, as HTTP is stateless, ASP.Net includes some tricks for persisting

state
across Page Requests. One is the PostBack. When the PostBack is received, it
contains the values in the Page, which are used to re-build the Page

class on the server in the state it was on the client. Without it, the Page form would be completely empty of values, as HTTP is stateless. Another is
ViewState. ViewState uses a hidden form field which is inserted into the
Page when the Response is sent to the browser. It contains the current

state
of all the form elements in the Page. When the Page Posts back, the
ViewState is read, and the new Page instance is re-populated with the

saved
state of the Page coming from the POST Request.

Note that this enables ONE PAGE class to remember the state IT was in

prior
to a PostBack. So, how do you persist data across multiple pages? After

all,
HTTP IS STATELESS (I'm going to keep repeating this so that you will get

it
drummed into your head - it is VERY important). Well, HTML has a mechanism for remembering a few things. It's called Cookies. So, when the first
Request for a Page comes from any client, the Session Collection has a new member added to it, with a unique ID, a Guid, that identifies the client
that sent the Request. This Guid is sent back to the client in the
Response.Cookies collection, as a Session Cookie (it is not saved on the
client, except during the current Session). Every time the browser makes a Request, it sends its Cookies in the Request header. The server reads the Session Cookie, and uses the Session object for that client during that
Request/Response.

So, are there any other ways to save the state of a User Control across
multiple page requests? Sure, but they all involve one thing: The client
must be uniquely identified on the server, so that the Page handling the
Request, which remembers nothing about any previous Requests (because HTTP IS STATELESS), can identify what client data to fetch for that Page. How

to
do that? Well, a Cookie comes to mind. You could create a Guid on the
server, and pass it to the client in the Response.Cookies Collection, and read it every time a new Request comes back. You would have to store both the Cookie Guid, and the User Control data somewhere. Now, you obviously
don't want to store it in memory, or you would probably use Session. You
could store it in a database, though, for example. Of course, as HTTP IS
STATELESS, and the server has no way to know when the client user has lost interest and navigated somewhere else, you would have to include some sort of Timeout process to remove the data from the database after a specified interval with no Requests.

This is, of course, how Session works. So you don't have to.

--
HTH,

Kevin Spencer
Microsoft MVP
.Net Developer
Ambiguity has a certain quality to it.

"McGeeky" <an**@anon.com> wrote in message
news:en*************@TK2MSFTNGP15.phx.gbl...
I should clarify:

I thought that there would be some **automatic** way for a user

control's viewstate to persist between pages without having to use the session.

Thanks

--
McGeeky
http://mcgeeky.blogspot.com
"McGeeky" <an**@anon.com> wrote in message
news:O3****************@tk2msftngp13.phx.gbl...
> My preference is that all state should be passed to each page as URL
> parameters to make testing and problem determination much easier.
>
> I thought that there would be some way for a user control's viewstate to> persist between pages without having to use the session.
>
> --
> McGeeky
> http://mcgeeky.blogspot.com
>
>
> "KMA" <km*@chum.com> wrote in message
> news:dj**********@atlas.ip-plus.net...
>> Well, the control state isn't "global", is it. It depends on the client,>> or
>> session of that client to be precise. What's your objection to using
>> session
>> state to store the state of the session?
>>
>>
>> "McGeeky" <an**@anon.com> wrote in message
>> news:Oz**************@TK2MSFTNGP09.phx.gbl...
>>> No. It could be different for each client
>>>
>>> --
>>> McGeeky
>>> http://mcgeeky.blogspot.com
>>>
>>>
>>> "KMA" <km*@chum.com> wrote in message
>> news:dj**********@atlas.ip-plus.net...
>>> > should the state of the UC be the same for all clients?
>>> >
>>> > "McGeeky" <an**@anon.com> wrote in message
>>> > news:uh**************@TK2MSFTNGP09.phx.gbl...
>>> >> Is there a way to get a user control to remember its state across>> pages?
>>> >> I
>>> >> have a standard page layout I use with a header and footer as user>>> > controls.
>>> >> Each page uses the same layout by means of copy paste (I hear this>>> >> will
>>> >> improve in ASP.Net 2 via master pages).
>>> >>
>>> >> When I navigate from one page to the next the header and footer user>>> >> controls lose their state because they are effectively different
>>> >> instances
>>> >> of the user control.
>>> >>
>>> >> Is there any way I can make the state of the user control exist
>>> >> between
>>> >> pages?
>>> >>
>>> >> Preferably without the use of hand coding the storing of data in the>>> > session
>>> >> or passing parameters to the user control on each page that includes>> it.
>>> > Is
>>> >> there a way of making the user control state "global"?
>>> >>
>>> >> Thanks!
>>> >>
>>> >> --
>>> >> McGeeky
>>> >> http://mcgeeky.blogspot.com
>>> >>
>>> >>
>>> >>
>>> >
>>> >
>>>
>>>
>>
>>
>
>



Nov 19 '05 #9
I appreciate that the session is a very useful feature. I have worked with
sessions many times before (not in ASP but JSP, from Java land) - but I just
don't like to load them up with data if I can help it at all.

Thanks for your feedback anyway. Its helped to shine some light in the dark
corners of my knowledge of ASP.Net.

--
McGeeky
http://mcgeeky.blogspot.com
"KMA" <km*@chum.com> wrote in message news:dj**********@atlas.ip-plus.net...
It would eat into bandwidth a bit. And by the time you've specified what
should and shouldn't be included you could have just coded the storage in
Session, which , after all, is the appropriate place.

You should have seen what things were like before Session.
"McGeeky" <an**@anon.com> wrote in message
news:OI**************@TK2MSFTNGP15.phx.gbl...
So, no, a user control cannot maintain state across pages without using

the
session.

Its a shame Microsoft don't extend viewstate beyond a single page because

it
would be very useful.

--
McGeeky
http://mcgeeky.blogspot.com
"Kevin Spencer" <ke***@DIESPAMMERSDIEtakempis.com> wrote in message
news:e8**************@TK2MSFTNGP15.phx.gbl...
> HTTP is stateless. An HTTP Request is received by the web server. It hands > it off the the ASP.Net application. The application identifies the handler > for that Request (a Page class). The Page class is instantiated and

handles
> the Request. It sends a Response to the client. Then it goes out of scope, > off into NothingLand. The next Request comes for a Page. The same thing
> happens again.
>
> Now, as HTTP is stateless, ASP.Net includes some tricks for persisting

state
> across Page Requests. One is the PostBack. When the PostBack is received,
it
> contains the values in the Page, which are used to re-build the Page

class > on the server in the state it was on the client. Without it, the Page form > would be completely empty of values, as HTTP is stateless. Another is
> ViewState. ViewState uses a hidden form field which is inserted into
> the
> Page when the Response is sent to the browser. It contains the current

state
> of all the form elements in the Page. When the Page Posts back, the
> ViewState is read, and the new Page instance is re-populated with the

saved
> state of the Page coming from the POST Request.
>
> Note that this enables ONE PAGE class to remember the state IT was in

prior
> to a PostBack. So, how do you persist data across multiple pages? After

all,
> HTTP IS STATELESS (I'm going to keep repeating this so that you will
> get

it
> drummed into your head - it is VERY important). Well, HTML has a mechanism > for remembering a few things. It's called Cookies. So, when the first
> Request for a Page comes from any client, the Session Collection has a new > member added to it, with a unique ID, a Guid, that identifies the
> client
> that sent the Request. This Guid is sent back to the client in the
> Response.Cookies collection, as a Session Cookie (it is not saved on
> the
> client, except during the current Session). Every time the browser
> makes a > Request, it sends its Cookies in the Request header. The server reads the > Session Cookie, and uses the Session object for that client during that
> Request/Response.
>
> So, are there any other ways to save the state of a User Control across
> multiple page requests? Sure, but they all involve one thing: The
> client
> must be uniquely identified on the server, so that the Page handling
> the
> Request, which remembers nothing about any previous Requests (because HTTP > IS STATELESS), can identify what client data to fetch for that Page.
> How

to
> do that? Well, a Cookie comes to mind. You could create a Guid on the
> server, and pass it to the client in the Response.Cookies Collection, and > read it every time a new Request comes back. You would have to store both > the Cookie Guid, and the User Control data somewhere. Now, you
> obviously
> don't want to store it in memory, or you would probably use Session.
> You
> could store it in a database, though, for example. Of course, as HTTP
> IS
> STATELESS, and the server has no way to know when the client user has lost > interest and navigated somewhere else, you would have to include some sort > of Timeout process to remove the data from the database after a specified > interval with no Requests.
>
> This is, of course, how Session works. So you don't have to.
>
> --
> HTH,
>
> Kevin Spencer
> Microsoft MVP
> .Net Developer
> Ambiguity has a certain quality to it.
>
> "McGeeky" <an**@anon.com> wrote in message
> news:en*************@TK2MSFTNGP15.phx.gbl...
> >I should clarify:
> >
> > I thought that there would be some **automatic** way for a user

control's
> > viewstate to persist between pages without having to use the session.
> >
> > Thanks
> >
> > --
> > McGeeky
> > http://mcgeeky.blogspot.com
> >
> >
> > "McGeeky" <an**@anon.com> wrote in message
> > news:O3****************@tk2msftngp13.phx.gbl...
> >> My preference is that all state should be passed to each page as URL
> >> parameters to make testing and problem determination much easier.
> >>
> >> I thought that there would be some way for a user control's
> >> viewstate

to
> >> persist between pages without having to use the session.
> >>
> >> --
> >> McGeeky
> >> http://mcgeeky.blogspot.com
> >>
> >>
> >> "KMA" <km*@chum.com> wrote in message
> >> news:dj**********@atlas.ip-plus.net...
> >>> Well, the control state isn't "global", is it. It depends on the

client,
> >>> or
> >>> session of that client to be precise. What's your objection to
> >>> using
> >>> session
> >>> state to store the state of the session?
> >>>
> >>>
> >>> "McGeeky" <an**@anon.com> wrote in message
> >>> news:Oz**************@TK2MSFTNGP09.phx.gbl...
> >>>> No. It could be different for each client
> >>>>
> >>>> --
> >>>> McGeeky
> >>>> http://mcgeeky.blogspot.com
> >>>>
> >>>>
> >>>> "KMA" <km*@chum.com> wrote in message
> >>> news:dj**********@atlas.ip-plus.net...
> >>>> > should the state of the UC be the same for all clients?
> >>>> >
> >>>> > "McGeeky" <an**@anon.com> wrote in message
> >>>> > news:uh**************@TK2MSFTNGP09.phx.gbl...
> >>>> >> Is there a way to get a user control to remember its state across > >>> pages?
> >>>> >> I
> >>>> >> have a standard page layout I use with a header and footer as user > >>>> > controls.
> >>>> >> Each page uses the same layout by means of copy paste (I hear this > >>>> >> will
> >>>> >> improve in ASP.Net 2 via master pages).
> >>>> >>
> >>>> >> When I navigate from one page to the next the header and footer

user
> >>>> >> controls lose their state because they are effectively
> >>>> >> different
> >>>> >> instances
> >>>> >> of the user control.
> >>>> >>
> >>>> >> Is there any way I can make the state of the user control exist
> >>>> >> between
> >>>> >> pages?
> >>>> >>
> >>>> >> Preferably without the use of hand coding the storing of data
> >>>> >> in

the
> >>>> > session
> >>>> >> or passing parameters to the user control on each page that

includes
> >>> it.
> >>>> > Is
> >>>> >> there a way of making the user control state "global"?
> >>>> >>
> >>>> >> Thanks!
> >>>> >>
> >>>> >> --
> >>>> >> McGeeky
> >>>> >> http://mcgeeky.blogspot.com
> >>>> >>
> >>>> >>
> >>>> >>
> >>>> >
> >>>> >
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >
> >
>
>



Nov 19 '05 #10

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

4
by: Guadala Harry | last post by:
Is there any way for one Session to remove and update objects in another Session? I seriously doubt it, but thought I'd ask. Here's why: I have some data that is unique per user (or per session -...
1
by: Praveen | last post by:
In user control I need to store some data. This data should be available across many pages where control is used. Currently I am using session to store it. Can this be done in a better way by...
5
by: Mike | last post by:
I have the need to keep a substantial amount of session state, but I do not have the option of using the HttpSessionState object. My current scheme for dealing with this is to convert all the...
7
by: Simon Harvey | last post by:
Hi everyone, I'm having a frustrating problem and I don't know how to fix it without totally redoing a very complicated couple of pages on my site. I really hope some kind soul can help me :-) ...
7
by: jsale | last post by:
I'm currently using ASP.NET with VS2003 and SQL Server 2003. The ASP.NET app i have made is running on IIS v6 and consists of a number of pages that allow the user to read information from the...
4
by: Sam | last post by:
I have an asp.net 2.0 app that uses a sitemap, Master Page, and has several content pages. While this feature has simplified the process of creating a data-driven site menu, it does seem to have...
0
by: RSH | last post by:
I am struggling with a concept I'm not really finding a lot of in depth articles on but Im sure others have had similar issues. What is the best practice when it comes to persisting custom...
20
by: luqman | last post by:
If user login with the login control in ASP.Net 2005 and then just close the browser and then open the browser again, the login status shows, User still Login? Any idea, how to Logout the User...
3
by: =?Utf-8?B?RHVrZSAoQU4yNDcp?= | last post by:
The majority of pages on our site need authentication (forms auth against the aspnetdb database). I created an '~/auth' folder with its own config file forcing authentication for any pages in the...
0
by: Vimpel783 | last post by:
Hello! Guys, I found this code on the Internet, but I need to modify it a little. It works well, the problem is this: Data is sent from only one cell, in this case B5, but it is necessary that data...
0
by: jfyes | last post by:
As a hardware engineer, after seeing that CEIWEI recently released a new tool for Modbus RTU Over TCP/UDP filtering and monitoring, I actively went to its official website to take a look. It turned...
0
by: ArrayDB | last post by:
The error message I've encountered is; ERROR:root:Error generating model response: exception: access violation writing 0x0000000000005140, which seems to be indicative of an access violation...
1
by: CloudSolutions | last post by:
Introduction: For many beginners and individual users, requiring a credit card and email registration may pose a barrier when starting to use cloud servers. However, some cloud server providers now...
1
by: Defcon1945 | last post by:
I'm trying to learn Python using Pycharm but import shutil doesn't work
1
by: Shællîpôpï 09 | last post by:
If u are using a keypad phone, how do u turn on JavaScript, to access features like WhatsApp, Facebook, Instagram....
0
by: af34tf | last post by:
Hi Guys, I have a domain whose name is BytesLimited.com, and I want to sell it. Does anyone know about platforms that allow me to list my domain in auction for free. Thank you
0
by: Faith0G | last post by:
I am starting a new it consulting business and it's been a while since I setup a new website. Is wordpress still the best web based software for hosting a 5 page website? The webpages will be...
0
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 3 Apr 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome former...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.