Provides access to behaviors and properties of environment window frames, for both tool and document windows.
Assembly: Microsoft.VisualStudio.Shell.Interop (in Microsoft.VisualStudio.Shell.Interop.dll)
Thetype exposes the following members.
|CloseFrame||Closes a window.|
|GetFramePos||Returns the position of the window.|
|GetGuidProperty||Returns a window frame property based on a supplied GUID.|
|GetProperty||Returns a window property.|
|Hide||Hides a window.|
|IsOnScreen||Returns true if the window frame is on the screen.|
|IsVisible||Determines whether or not the window is visible.|
|QueryViewInterface||Provides with a view helper (VSFPROPID_ViewHelper) inserted into its list of event notifications.|
|SetFramePos||Sets the position of the window.|
|SetGuidProperty||Sets a window frame property based on a supplied GUID.|
|SetProperty||Sets a window frame property.|
|Show||Renders this window visible, brings the window to the top, and activates the window.|
|ShowNoActivate||Shows or makes a window visible and brings it to the top, but does not make it the active window.|
The environment does not provide two modes for controls hosted in an IVsWindowFrame object. A check for ambient properties returns null indicating that ambient properties are not supported.
A VSPackage that implements IOleObject, such as an editor that uses a document window, might call the GetAmbientUserMode method to check for design mode or run mode. While the guidelines for ActiveX control containers state that the containers (or sites) should support ambient properties, this doesn't work in Visual Studio because the site created for the VSPackage does not support ambient properties.
UserMode normally indicates the mode in which the control should be run:
UserMode == false
UserMode == trueNotes to Callers
Call IVsWindowFrame to obtain an IVsWindowFrame pointer to call methods on a document or tool window. IVsWindowFrame is implemented by the environment through the SVsWindowFrame service.