WOW.NET

The WOW.NET control's interface is identical to the WOW control, except that it's events interface is optimized for .NET (please see below).

But why an ActiveX Control?

The obvious question is, "why is it an ActiveX control and not a pure .NET control"?  There are two main reasons.  The first is that, in order to hook into the webbrowser control, it requires unmanaged C++ and COM. There is simply no other way.  Additionally, the webbrowser control requires having its IOleInPlaceActiveObject::TranslateAccelerator method called, which won't happen when wrapped by a .NET UserControl.  Without these features, tabbing between fields and other controls on the form won't work, and we would not be able to implement the other cool features of WOW. For these reasons, it must be ActiveX.

WOW.NET is optimized for .NET

The IWowCtl2Events interface of the .NET version does not use dispinterface for its events, but rather a custom interface (meaning derived from IUnknown).  This means that the events will be lightning fast because they don't go through the IDispatch::Invoke mechanism, but rather will go through v-table invocation (much faster).

WOW.NET is identical to the WOW control otherwise. Please see the WOW product page for details.