Request.Form with Masterpage

[sck10]

Hello,

How do you use Request.Form["HiddenFiel d"] when the first page is using a
MasterPage?

Thanks, sck10

[Steven Cheng[MSFT]]

Hello Steve,

Do you mean in the original page, the hidden fields are put on MasterPage's
content? If so, this does make the identification of the hidden
fields(form items) in target page abit difficult. Becaue for controls put
in Master page, its name and id will be mangled. For example, the following
html control in master page

=========
<input id="hidden1" name="hidden1" runat="server" type="hidden"
value="hidden1 value" />
<input id="hidden2" name="hidden2" runat="server" type="hidden"
value="hidden2 value" />
===========

will be rendered as below finally:

<input name="ctl00$hid den1" type="hidden" id="ctl00_hidde n1"
value="hidden1 value" />
<input name="ctl00$hid den2" type="hidden" id="ctl00_hidde n2"
value="hidden2 value" />

Thus, on the target page, you can not directly use the original
hiddenfield's name to quey the Request.Form collection. One flexible means
is to query the Request.Form collection and find the one that contains the
hiddenfield's unmangled name. e.g.

========in target page=========== ====

protected void Page_Load(objec t sender, EventArgs e)
{
foreach (string key in Request.Form.Ke ys)
{
if(key.Contains ("hidden1"))
Response.Write( "<br/>" + key + ": " + Request.Form[key]);
}
}
=============== ===============

Hope this helps.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

=============== =============== =============== =====

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.

=============== =============== =============== =====

This posting is provided "AS IS" with no warranties, and confers no rights.

[Olaf Rabbachin]

Hi,

Steven Cheng[MSFT] wrote:

Becaue for controls put in Master page, its name and id will be mangled.

.... which you can work around by using the .ClientID-property.

Cheers,
Olaf
--
My .02: www.Resources.IntuiDev.com

[Steven Cheng[MSFT]]

Hi Olaf,

thanks for your input.

I think what you mentioned should be "Control.Unique ID" :)

http://msdn2.microsoft.com/en-us/lib....uniqueid(VS.8
0).aspx

BTW, the problem here is that he is cross post to a remote page on
different server, this "UniqueID" is not workable.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.

[sck10]

Thanks Walter, I will try your suggestion.

"Steven Cheng[MSFT]" <st*****@online .microsoft.comw rote in message
news:gt******** ******@TK2MSFTN GXA01.phx.gbl.. .

Hello Steve,

Do you mean in the original page, the hidden fields are put on
MasterPage's
content? If so, this does make the identification of the hidden
fields(form items) in target page abit difficult. Becaue for controls put
in Master page, its name and id will be mangled. For example, the
following
html control in master page

=========
<input id="hidden1" name="hidden1" runat="server" type="hidden"
value="hidden1 value" />
<input id="hidden2" name="hidden2" runat="server" type="hidden"
value="hidden2 value" />
===========

will be rendered as below finally:

<input name="ctl00$hid den1" type="hidden" id="ctl00_hidde n1"
value="hidden1 value" />
<input name="ctl00$hid den2" type="hidden" id="ctl00_hidde n2"
value="hidden2 value" />

Thus, on the target page, you can not directly use the original
hiddenfield's name to quey the Request.Form collection. One flexible means
is to query the Request.Form collection and find the one that contains the
hiddenfield's unmangled name. e.g.

========in target page=========== ====

protected void Page_Load(objec t sender, EventArgs e)
{
foreach (string key in Request.Form.Ke ys)
{
if(key.Contains ("hidden1"))
Response.Write( "<br/>" + key + ": " + Request.Form[key]);
}
}
=============== ===============

Hope this helps.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

>

[Steven Cheng[MSFT]]

Thanks for your reply Steve,

Please feel free to let me know if you meet any further problem.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.

[Olaf Rabbachin]

Hi,

Steven Cheng[MSFT] wrote:

I think what you mentioned should be "Control.Unique ID" :)

sorry for my posting, I wasn't reading carefully enough and assumed a
client-side thing (i.e. some JavaScript looking for the control). :-P

Cheers,
Olaf
--
My .02: www.Resources.IntuiDev.com