G
Guest
I'm working for a company in Houston developing a web application. At one
point in the code, we have to refresh the page, but save what checkboxes have
been selected. Since these checkboxes are created programmatically according
to configuration files, they cannot be asp checkboxes.
To do this, before refreshing I save which checkboxes are selected to an asp
textbox and perform a postback. Later in the .aspx file, I have a <% %>
block that calls a method from the codebehind to output a Javascript call.
However, in this codebehind C# call, when I access the textbox's .Text field,
it is always empty, regardless of the actual values put in the text box. The
really strange part of it is that when the page refreshes, the asp textbox
has the correct values in the input tag's value attribute.
Is there some wierd execution order to ASP.NET that I am unaware of that
would cause this? And, more importantly, is there a way around it? any help
would be greatly appreciated.
point in the code, we have to refresh the page, but save what checkboxes have
been selected. Since these checkboxes are created programmatically according
to configuration files, they cannot be asp checkboxes.
To do this, before refreshing I save which checkboxes are selected to an asp
textbox and perform a postback. Later in the .aspx file, I have a <% %>
block that calls a method from the codebehind to output a Javascript call.
However, in this codebehind C# call, when I access the textbox's .Text field,
it is always empty, regardless of the actual values put in the text box. The
really strange part of it is that when the page refreshes, the asp textbox
has the correct values in the input tag's value attribute.
Is there some wierd execution order to ASP.NET that I am unaware of that
would cause this? And, more importantly, is there a way around it? any help
would be greatly appreciated.