.netwebbrowser-controlapi-design

Is using the WebBrowser object for an API bad?

I plan on making an API for a cool web site I found in VB.net. The easiest method at my disposal is to create a WebBrowser object, hide it, and then force it to do all the dirty work.

Now, is this a bad idea? Is this too hacked up to be useful?

Solution

  • You can use WebClient instead. It has no interface to be hidden.