I'm running into an unusual one that I can't explain and hoping someone can enlighten me. I've got an XBAP app that interacts with the default.aspx (ASP.NET) page through the BrowserInteropHelper.HostScript object to call a javascript function. This functionality works just fine from the root XBAP application, but our app can open up new WPF Windows. When trying to access the HostScript from these new Windows we are getting null returned. The parent object is still showing as a web browser, but no joy.
In WPF, when you create a "new Window()" in an XBAP app is this window still running under IE or running as a desktop window? Is there a way to indicate the new window should run inside an IE iframe or inject the HostScript some how so the window has access to it?
Basically I'm trying to block the IE Help command from opening using JavaScript which works great in the main page but new windows still launch the IE Help as well as my own when using F1.