Client Side Web Request and auto-submitting ASP.Net pages

[Rick Strahl [MVP]]

Run into an interesting problem today with a client of mine:

They have an ASP.Net form that they want to drive through a client side HTTP
interface. I know a Web Service would be a better way to go but in this case
they want to try and consolidate a single interface for the 3 or 4 forms
involved and drive them through a WebRequest Http client.

The data is getting there no problem - it's retrievable with
Request.Form["formfield"]. However ASP.net is not doing anything to fire
events or even assign the data back to the original form fields.

Anybody know of a way to trigger ASP.Net to force it to read and assign the
form variables and fire events?

I think the problem is likely to be viewstate (even though it's disabled
there's still viewstate being placed on the form), but even when I post back
the viewstate from the 'base' page it doesn't work.

This seems like a fairly major issue if there is no workaround since you
basically cannot drive HTML remotely through ASP.Net forms...

Any ideas how to make this work?

+++ Rick ---

--

Rick Strahl
West Wind Technologies
http://www.west-wind.com/
http://www.west-wind.com/weblog/
----------------------------------
Making waves on the Web

[bruce barker]

there is no problem driving an asp.net site thru a http client. you are
correct, you need to pass back the valid viewstate that came with the page.
to fire events you need to emulate browser behavior.

when the client requests (gets) the form how are you parsing the html to get
the viewstate.
when the client posts the form back, it needs to send the submit button
value, for the button to firte an event.
when the client post back from a non-submit control, it has to fill in the
postback hidden fields.

also what user agent is the client using, and how is it supporting cookies?

-- bruce (sqlwork.com)

"Rick Strahl [MVP]" <ri********@hot mail.com> wrote in message
news:eB******** ******@TK2MSFTN GP12.phx.gbl...

Run into an interesting problem today with a client of mine:

They have an ASP.Net form that they want to drive through a client side HTTP interface. I know a Web Service would be a better way to go but in this case they want to try and consolidate a single interface for the 3 or 4 forms
involved and drive them through a WebRequest Http client.

The data is getting there no problem - it's retrievable with
Request.Form["formfield"]. However ASP.net is not doing anything to fire
events or even assign the data back to the original form fields.

Anybody know of a way to trigger ASP.Net to force it to read and assign the form variables and fire events?

I think the problem is likely to be viewstate (even though it's disabled
there's still viewstate being placed on the form), but even when I post back the viewstate from the 'base' page it doesn't work.

This seems like a fairly major issue if there is no workaround since you
basically cannot drive HTML remotely through ASP.Net forms...

Any ideas how to make this work?

+++ Rick ---

--

Rick Strahl
West Wind Technologies
http://www.west-wind.com/
http://www.west-wind.com/weblog/
----------------------------------
Making waves on the Web

[Lostinet.Web Support]

something like this ?
http://www.lostinet.com/en/lwsamplecs/?framesrc=rane/
is my remote scripting . free .

--
http://www.lostinet.com/
---------------------------
Lostinet.Web Controls&Compon ents help you to build better Asp.Net
CustomerControl &UserControl&Ap plication.
---------------------------
It's FREE !!
---------------------------
ControlHelper&H elperElement for MessageBox&Dial og
ComboBox,ComboC alendar,SmartIf rame
---------------------------
Remote Asp.Net Execution

"Rick Strahl [MVP]" <ri********@hot mail.com> дÈëÓʼþ
news:eB******** ******@TK2MSFTN GP12.phx.gbl...

Run into an interesting problem today with a client of mine:

They have an ASP.Net form that they want to drive through a client side HTTP interface. I know a Web Service would be a better way to go but in this case they want to try and consolidate a single interface for the 3 or 4 forms
involved and drive them through a WebRequest Http client.

The data is getting there no problem - it's retrievable with
Request.Form["formfield"]. However ASP.net is not doing anything to fire
events or even assign the data back to the original form fields.

Anybody know of a way to trigger ASP.Net to force it to read and assign the form variables and fire events?

I think the problem is likely to be viewstate (even though it's disabled
there's still viewstate being placed on the form), but even when I post back the viewstate from the 'base' page it doesn't work.

This seems like a fairly major issue if there is no workaround since you
basically cannot drive HTML remotely through ASP.Net forms...

Any ideas how to make this work?

+++ Rick ---

--

Rick Strahl
West Wind Technologies
http://www.west-wind.com/
http://www.west-wind.com/weblog/
----------------------------------
Making waves on the Web