IWebViewCreateInspectorView Method (WebSession, Boolean)Awesomium.NET 1.7.6Awesomium.NET
Requests the creation of a special Developer Tools Inspector View, that inspects the web contents of this view.

Namespace: Awesomium.Core
Assembly: Awesomium.Core (in Awesomium.Core.dll) Version:

void CreateInspectorView(
	WebSession session,
	bool docked = false


Type: Awesomium.CoreWebSession
A WebSession instance to associate with this Inspector View. If it's an on-disk session, it can be used for saving Inspector settings and session details.
docked (Optional)
Type: SystemBoolean
Specifies if the Developer Tools frontend layout, should initially appear as docked. (Default: false)

InvalidOperationException The member is called on an invalid view. (See: IsLive)
InvalidOperationException A Developer Tools Inspector view, is already associated with this view. Dispose it before you create another.
ObjectDisposedException The specified session is disposed.
ArgumentException Only sessions created with Default preferences can be used with an Inspector View.

An Inspector View is a special IWebView instance dedicated to loading the Awesomium Developer Tools to inspect the contents of another IWebView, locally. Inspector Views are associated with the view they inspect and they provide specific API that allows users interact with the Developer Tools frontend.
Note Note
Inspector Views do not require activating remote debugging when initializing the WebCore (see: RemoteDebuggingHost and RemoteDebuggingPort).


The following list presents details for creating and wrapping an Inspector View:


To interact with the Developer Tools frontend loaded by an Inspector View, acquire the IWebViewInspector service by calling GetService(Type) on the Inspector View.

The IWebViewInspector service provides methods and events that allow you to control the Developer Tools UI and monitor user actions on the Inspector View or the inspected IWebView instance.


Developer Tools Inspector IWebView instances allow a minimum set of operations to be performed on them. The following list presents operations that cannot be performed on a Developer Tools Inspector view:

More Details


You should dispose an Inspector View (and optionally its associated WebSession), just like any other IWebView when you're done with it. The following list indicates when an Inspector View falls out of use and therefore its container should be closed and the Inspector View be disposed:
  • When its containing standalone tool-window is closed.
  • When the CloseInspectorView event is fired in response to the user asking to close a docked Inspector View by clicking the Close button on the Developer Tools frontend.
  • When the InspectedViewClosing event is fired indicating that the inspected view has been disposed.
See Also