Assembly: Microsoft.VisualStudio.Shell.Interop (in microsoft.visualstudio.shell.interop.dll)
[GuidAttribute("0F4B629E-8C34-4B5E-A450-F9F8DCFE3009")] [InterfaceTypeAttribute(1)] public interface IVsMultiViewDocumentView
/** @attribute GuidAttribute("0F4B629E-8C34-4B5E-A450-F9F8DCFE3009") */ /** @attribute InterfaceTypeAttribute(1) */ public interface IVsMultiViewDocumentView
rguidLogicalView parameter of InitializeEditorInstance. This determines which view is activated when the editor window is shown when the editor is instantiated.checks to see if the document view object implements IVsMultiViewDocumentView. If it does, InitializeEditorInstance calls passing in the GUID of the logical view that was passed into the
By specifying the logical view GUID, the caller of InitializeEditorInstance is able to request the specific view that matches the reason the caller is requesting the view. For example, the caller would specifyto get the view appropriate for debugging view, or to get the view appropriate for the text editor (that is, a view that implements ).
The Visual Studio Environment SDK does not limit developers to any particular implementation of multiple view. A VSPackage might implement a multiview document as split-screen, tabbed or other type of display.
The environment SDK itself does not provide native support for the various types of displays. The specific implementation a given type of display requires is done through standard windows programming.