The 2.0 WebBrowser control is a wonderful thing, but handling navigation to
a new browser window seems to need access to NewWindow2, which unfortunately
is not part of the package. Any practical suggestions/code samples on how
to
make this work?

In theory it should be possible to hook the unmanaged event, create a new
managed control and get an object from it to pass back to the event caller.
Sounds hairy to me -- anyone tried it?

All suggestions much appreciated.

DavidB