1<?xml version="1.0" encoding="utf-8"?>
2<Type Name="ViewTechnology" FullName="System.ComponentModel.Design.ViewTechnology">
3  <TypeSignature Language="C#" Maintainer="auto" Value="public enum ViewTechnology" />
4  <TypeSignature Language="ILAsm" Value=".class public auto ansi sealed ViewTechnology extends System.Enum" />
5  <AssemblyInfo>
6    <AssemblyName>System</AssemblyName>
7    <AssemblyPublicKey>[00 00 00 00 00 00 00 00 04 00 00 00 00 00 00 00]</AssemblyPublicKey>
8    <AssemblyVersion>1.0.3300.0</AssemblyVersion>
9    <AssemblyVersion>1.0.5000.0</AssemblyVersion>
10    <AssemblyVersion>2.0.0.0</AssemblyVersion>
11    <AssemblyVersion>4.0.0.0</AssemblyVersion>
12  </AssemblyInfo>
13  <ThreadSafetyStatement>Gtk# is thread aware, but not thread safe; See the &lt;link location="node:gtk-sharp/programming/threads"&gt;Gtk# Thread Programming&lt;/link&gt; for details.</ThreadSafetyStatement>
14  <Base>
15    <BaseTypeName>System.Enum</BaseTypeName>
16  </Base>
17  <Attributes>
18    <Attribute>
19      <AttributeName>System.Runtime.InteropServices.ComVisible(true)</AttributeName>
20    </Attribute>
21  </Attributes>
22  <Docs>
23    <remarks>
24      <attribution license="cc4" from="Microsoft" modified="false" />
25      <para>The view adapter model replaces and adds functionality to the <see cref="T:System.ComponentModel.Design.ViewTechnology" /> feature; however, the <see cref="T:System.ComponentModel.Design.ViewTechnology" /> 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.</para>
26      <para>
27        <see cref="T:System.ComponentModel.Design.ViewTechnology" /> defines identifiers that can indicate the mode to use for controlling the display of a designer-hosted document.</para>
28      <para>You should only use the <see cref="F:System.ComponentModel.Design.ViewTechnology.Default" /> value in your designer hosting environment. In previous versions of the dnprdnshort, the <see cref="T:System.ComponentModel.Design.ViewTechnology" /> enumeration specified the type of UI model supported by a root designer. Because this model is not extensible, you should instead use a <newTerm>view adapter</newTerm> model. A view adapter is a type that adapts an object of one type to another. </para>
29      <para>For example, an HTML designer might return a DemoDOM tree as its view. The HTML designer returns a view technology of <see cref="F:System.ComponentModel.Design.ViewTechnology.Default" />. 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 <see cref="M:System.ComponentModel.Design.IRootDesigner.GetView(System.ComponentModel.Design.ViewTechnology)" /> method, the load of the designer will fail, and the user will be presented with an error.</para>
30      <para>vsprvs 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. </para>
31      <para>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. </para>
32    </remarks>
33    <summary>
34      <attribution license="cc4" from="Microsoft" modified="false" />
35      <para>Defines identifiers for a set of technologies that designer hosts support.</para>
36    </summary>
37  </Docs>
38  <Members>
39    <Member MemberName="Default">
40      <MemberSignature Language="C#" Value="Default" />
41      <MemberSignature Language="ILAsm" Value=".field public static literal valuetype System.ComponentModel.Design.ViewTechnology Default = int32(2)" />
42      <MemberType>Field</MemberType>
43      <AssemblyInfo>
44        <AssemblyVersion>2.0.0.0</AssemblyVersion>
45        <AssemblyVersion>4.0.0.0</AssemblyVersion>
46      </AssemblyInfo>
47      <ReturnValue>
48        <ReturnType>System.ComponentModel.Design.ViewTechnology</ReturnType>
49      </ReturnValue>
50      <Docs>
51        <remarks>
52          <attribution license="cc4" from="Microsoft" modified="false" />
53          <para>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 vsprvs provide a way to plug in new view technology adapters. The default view object for the Windows Forms designer is a <see cref="T:System.Windows.Forms.Control" /> instance.</para>
54        </remarks>
55        <summary>
56          <attribution license="cc4" from="Microsoft" modified="false" />
57          <para>Specifies the default view technology support. </para>
58        </summary>
59      </Docs>
60    </Member>
61    <Member MemberName="Passthrough">
62      <MemberSignature Language="C#" Value="Passthrough" />
63      <MemberSignature Language="ILAsm" Value=".field public static literal valuetype System.ComponentModel.Design.ViewTechnology Passthrough = int32(0)" />
64      <MemberType>Field</MemberType>
65      <AssemblyInfo>
66        <AssemblyVersion>1.0.5000.0</AssemblyVersion>
67        <AssemblyVersion>2.0.0.0</AssemblyVersion>
68        <AssemblyVersion>4.0.0.0</AssemblyVersion>
69      </AssemblyInfo>
70      <Attributes>
71        <Attribute>
72          <AttributeName>System.Obsolete("Use ViewTechnology.Default.")</AttributeName>
73        </Attribute>
74      </Attributes>
75      <ReturnValue>
76        <ReturnType>System.ComponentModel.Design.ViewTechnology</ReturnType>
77      </ReturnValue>
78      <Parameters />
79      <Docs>
80        <remarks>
81          <attribution license="cc4" from="Microsoft" modified="false" />
82          <para>The view object must implement any interfaces the development environment requires. The vsprvs 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 vsprvs VSI (vsprvs Integration) program. The vsprvs development environment provides support for this view technology. Support for this view technology is not necessarily available in all development environments.</para>
83        </remarks>
84        <summary>
85          <attribution license="cc4" from="Microsoft" modified="false" />
86          <para>Represents a mode in which the view object is passed directly to the development environment. </para>
87        </summary>
88      </Docs>
89    </Member>
90    <Member MemberName="WindowsForms">
91      <MemberSignature Language="C#" Value="WindowsForms" />
92      <MemberSignature Language="ILAsm" Value=".field public static literal valuetype System.ComponentModel.Design.ViewTechnology WindowsForms = int32(1)" />
93      <MemberType>Field</MemberType>
94      <AssemblyInfo>
95        <AssemblyVersion>1.0.5000.0</AssemblyVersion>
96        <AssemblyVersion>2.0.0.0</AssemblyVersion>
97        <AssemblyVersion>4.0.0.0</AssemblyVersion>
98      </AssemblyInfo>
99      <Attributes>
100        <Attribute>
101          <AttributeName>System.Obsolete("Use ViewTechnology.Default.")</AttributeName>
102        </Attribute>
103      </Attributes>
104      <ReturnValue>
105        <ReturnType>System.ComponentModel.Design.ViewTechnology</ReturnType>
106      </ReturnValue>
107      <Parameters />
108      <Docs>
109        <remarks>
110          <attribution license="cc4" from="Microsoft" modified="false" />
111          <para>The designer host fills the development environment document window with the Windows Forms control.</para>
112        </remarks>
113        <summary>
114          <attribution license="cc4" from="Microsoft" modified="false" />
115          <para>Represents a mode in which a Windows Forms control object provides the display for the root designer. </para>
116        </summary>
117      </Docs>
118    </Member>
119  </Members>
120</Type>