Defines identifiers for a set of technologies that designer hosts support.
Assembly: System (in System.dll)
|Specifies the default view technology support. |
The root designer may return any type of object, but the object must be compatible with an adapter for the technology of the host. Hosting environments such as Visual Studio provide a way to plug in new view technology adapters. The default view object for the Windows Forms designer is a System.Windows.Forms.Control instance.
| Obsolete. Represents a mode in which the view object is passed directly to the development environment. |
The view object must implement any interfaces the development environment requires. The Visual Studio development environment supports view objects that are either an ActiveX control, active document, or an object that implements the IVsWindowPane interface that is available through Visual Studio VSI (Visual Studio Integration) program. The Visual Studio development environment provides support for this view technology. Support for this view technology is not necessarily available in all development environments.
| Obsolete. Represents a mode in which a Windows Forms control object provides the display for the root designer. |
The designer host fills the development environment document window with the Windows Forms control.
The view adapter model replaces and adds functionality to the feature; however, the feature is retained for both backward compatibility and future use, if you choose. For more information, see ".NET Shape Library: A Sample Designer" in the Windows Forms Knowledge Base at http://windowsforms.net/articles/shapedesigner.aspx.
defines identifiers that can indicate the mode to use for controlling the display of a designer-hosted document.
You should only use the value in your designer hosting environment. In previous versions of the .NET Framework, the enumeration specified the type of UI model supported by a root designer. Because this model is not extensible, you should instead use a view adapter model. A view adapter is a type that adapts an object of one type to another.
For example, an HTML designer might return a DemoDOM tree as its view. The HTML designer returns a view technology of . A Windows Forms hosting environment would have one or more view adapter classes available. If one such class could convert the DemoDOM into a Windows Forms control, the hosting application can support this type of designer. If no adapter can handle the data type returned from the designer’s GetView method, the load of the designer will fail, and the user will be presented with an error.
Visual Studio has an extensible scheme for providing view adapters, so it can adapt to any UI technology. Third-party technology providers can also offer an appropriate view adapter, and their object models are immediately consumable.
For an example that uses view adapters, see ".NET Shape Library: A Sample Designer" in the Windows Forms Knowledge Base at http://windowsforms.net/articles/shapedesigner.aspx.