I am working on a full-featured WPF browser (XBAP) and have run into a problem. The application on the client is connected to handle navigation requests with a specific prefix / protocol. (For example, "foo: // ...") In addition, the application processes them differently depending on which browser makes the request. I tried the "NavigationService.Navigate ()" method, but for some strange reason this includes WebRequest objects that throw a NotSupportedException: "The URI is not recognized." I can create a WebBrowser control and successfully navigate IT with this prefix, but the application recognizes it as a different browser and reacts differently. If I were using Silverlight, I would have to directly install the "window.location" browser, which works fine. But of course,this seems to be available only in Silverlight.
So what I need to do is launch the browser that hosts the XBAP in order to navigate to the URI with this special prefix.
Phew That is all I think. Thanks.
Updating ..Net Framework 4.0 will allow you to directly access the browser DOM, which will solve this problem, however, I'm still trying to find ways to achieve this in .Net 3.x.
source
share