I\'m trying to run an webpage inside a Webbrowser control wich contains a connection to an Websocket. The control can\'t connect to the Websocket. When I tested in IE, every
The problem is that the webbrowser control, while using the local IE as a basis, is more locked down (or maybe better to say "differently configured") by default.
The ability to control this is called Feature Control and you can read about it on MSDN here
In terms of solving your actual problems, a similar question has been solved with code provided in this answer to an equivalent question on C#. Note the tweaks in the subsequent answer as well.