Re: AxShDocVw.AxWebBrowser.Navigate and object headers
- From: "Marc Gravell" <marc.gravell@xxxxxxxxx>
- Date: Mon, 19 Nov 2007 11:15:13 -0000
The cited CodeProject article you refer is working client-side, not
client-server - meaning that the html at the client can talk to the
winform at the client, which is what I was discussing (window.external
aka WebBrowser.ObjectForScripting).
I think you need to clarify "web application" - do you mean the
web-server, or the html-client (including client-side javascript)?
There is a big difference. I suspect you mean the former (web-server),
but there is no /single/ (or standard) way of doing this:
You can automate things quite easily, but you need to be *very* clear
what data you are sending to where. A plain "object" isn't going to
work over the wire (client-server), but if there is an agreed
serialization format it might work; likewise, you can populate html
form elements and submit them from a host winform; this may be fine.
Or web-services / vanilla web-requests (without a browser) may be an
option.
Sorry if I'm not giving much of an answer, but the question is still
more-than-a-little vague...
Marc
.
- References:
- Re: AxShDocVw.AxWebBrowser.Navigate and object headers
- From: Marc Gravell
- Re: AxShDocVw.AxWebBrowser.Navigate and object headers
- Prev by Date: Re: Order or DbLinq properties in code generated by pgsqlmetal
- Next by Date: Re: Order or DbLinq properties in code generated by pgsqlmetal
- Previous by thread: Re: AxShDocVw.AxWebBrowser.Navigate and object headers
- Next by thread: Re: AxShDocVw.AxWebBrowser.Navigate and object headers
- Index(es):
Relevant Pages
|