0

What I'm trying to do is to, from a Web Service (WCF), give a remote computer (the Web Service Consumer) the instruction to open its default Web Browser (be it Internet Explorer, Firefox, Chrome, etc.), navigate to a certain web page and keep monitoring the events of that browser so that I can capture a certain value from the Document Title at a certain point, and do stuff with it.

I'm already able to send the command to open Internet Explorer and navigate to a URL, from the Web Service to the remote computer (my consumer), but I don't like the approach since I can't monitor the Document.Title property for changes nor access its value at any given time. Here is an example:

using System.Diagnostics;

public void DoIt();
{
  Process batchProcess = new Process();
  batchProcess.StartInfo.FileName = "iexplore.exe";
  batchProcess.StartInfo.Arguments = "http://whatever.com";
  batchProcess.Start();
}

This opens up Internet Explorer on the remote machine and navigates to the Url I give it, but I can't keep watch for the Browser's Events or Properties Values....

Can somebody help? ;-)

Arnie
  • 212
  • 1
  • 2
  • 11

1 Answers1

0

I don't think you can access information in one application (the web browser) from another (the WCF client) like that, and it's certainly not possible to do it without knowing what the user's default browser is.

You might have more luck using a WebBrowser control (WPF or Windows Forms), which embeds Internet Explorer's engine into the application and allows you access to the document title.

libertyernie
  • 2,590
  • 1
  • 17
  • 13
  • Wait a minute, how can a WebBrowser control be obtained or implemented in WCF? Because if that's the case then that's my solution right there but I'm thinking the control has to run on the consumer's PC because it has to take the user to a login page from there... You see what I'm really trying to implement is a Web service that handles social network authentication in an universal way so no matter which client wants to authenticate, the web service handles the oauth flow so that it doesn't have to be coded separately on each client app – Arnie Aug 10 '15 at 22:16
  • Oops, typo - that should be WPF – libertyernie Aug 11 '15 at 13:17