Promise to upload a demo app about this custom control when i get this working.
Any other idea?.
Posted By dejavu on 23 Feb 2012 06:58 AM
So, IE security policies get applied. Nothing to do with that. The only way as I see right now is to develop a custom totally from scratch WebBrowser control. That way, if original WebBrowser control has methods to override scripting security policies, perhaps it's possible to lower that policies, and finally get a WebBrowser control-like more permissive to scripting from others domains.
All this sounds like it works for me. But just in a couple of times I've done custom controls, and it was in the old ASP.NET 1.1 ages.