From 436afcf02496c33541936e6b9185f4a0e71c1308 Mon Sep 17 00:00:00 2001
From: "Andy (Steve) De George" <67293991+adegeo@users.noreply.github.com>
Date: Mon, 24 Jan 2022 11:07:36 -0800
Subject: [PATCH 1/3] minor updates to get new build (#1281)

---
 .../wpf/advanced/xaml-syntax-in-detail.md       | 17 +++++++++--------
 1 file changed, 9 insertions(+), 8 deletions(-)

diff --git a/dotnet-desktop-guide/framework/wpf/advanced/xaml-syntax-in-detail.md b/dotnet-desktop-guide/framework/wpf/advanced/xaml-syntax-in-detail.md
index 820c3b5f46..3d30cea348 100644
--- a/dotnet-desktop-guide/framework/wpf/advanced/xaml-syntax-in-detail.md
+++ b/dotnet-desktop-guide/framework/wpf/advanced/xaml-syntax-in-detail.md
@@ -33,6 +33,7 @@ helpviewer_keywords:
 ms.assetid: 67cce290-ca26-4c41-a797-b68aabc45479
 ---
 # XAML Syntax In Detail
+
 This topic defines the terms that are used to describe the elements of XAML syntax. These terms are used frequently throughout the remainder of this documentation, both for WPF documentation specifically and for the other frameworks that use XAML or the basic XAML concepts enabled by the XAML language support at the System.Xaml level. This topic expands on the basic terminology introduced in the topic [XAML in WPF](xaml-in-wpf.md).  
 
 <a name="the_xaml_language_specification"></a>
@@ -46,9 +47,9 @@ This topic defines the terms that are used to describe the elements of XAML synt
  XAML is a markup language. The common language runtime (CLR), as implied by its name, enables runtime execution. XAML is not by itself one of the common languages that is directly consumed by the CLR runtime. Instead, you can think of XAML as supporting its own type system. The particular XAML parsing system that is used by WPF is built on the CLR and the CLR type system. XAML types are mapped to CLR types to instantiate a run time representation when the XAML for WPF is parsed. For this reason, the remainder of discussion of syntax in this document will include references to the CLR type system, even though the equivalent syntax discussions in the XAML language specification do not. (Per the XAML language specification level, XAML types could be mapped to any other type system, which does not have to be the CLR, but that would require the creation and use of a different XAML parser.)  
   
 #### Members of Types and Class Inheritance  
- Properties and events as they appear as XAML members of a [!INCLUDE[TLA2#tla_winclient](../../../includes/tla2sharptla-winclient-md.md)] type are often inherited from base types. For example, consider this example: `<Button Background="Blue" .../>`. The <xref:System.Windows.Controls.Control.Background%2A> property is not an immediately declared property on the <xref:System.Windows.Controls.Button> class, if you were to look at the class definition, reflection results, or the documentation. Instead, <xref:System.Windows.Controls.Control.Background%2A> is inherited from the base <xref:System.Windows.Controls.Control> class.  
+ Properties and events as they appear as XAML members of a WPF type are often inherited from base types. For example, consider this example: `<Button Background="Blue" .../>`. The <xref:System.Windows.Controls.Control.Background%2A> property is not an immediately declared property on the <xref:System.Windows.Controls.Button> class, if you were to look at the class definition, reflection results, or the documentation. Instead, <xref:System.Windows.Controls.Control.Background%2A> is inherited from the base <xref:System.Windows.Controls.Control> class.  
   
- The class inheritance behavior of [!INCLUDE[TLA2#tla_winclient](../../../includes/tla2sharptla-winclient-md.md)] XAML elements is a significant departure from a schema-enforced interpretation of XML markup. Class inheritance can become complex, particularly when intermediate base classes are abstract, or when interfaces are involved. This is one reason that the set of XAML elements and their permissible attributes is difficult to represent accurately and completely using the schema types that are typically used for XML programming, such as DTD or XSD format. Another reason is that extensibility and type-mapping features of the XAML language itself preclude completeness of any fixed representation of the permissible types and members.  
+ The class inheritance behavior of WPF XAML elements is a significant departure from a schema-enforced interpretation of XML markup. Class inheritance can become complex, particularly when intermediate base classes are abstract, or when interfaces are involved. This is one reason that the set of XAML elements and their permissible attributes is difficult to represent accurately and completely using the schema types that are typically used for XML programming, such as DTD or XSD format. Another reason is that extensibility and type-mapping features of the XAML language itself preclude completeness of any fixed representation of the permissible types and members.  
   
 <a name="object_element_syntax"></a>
 ## Object Element Syntax  
@@ -69,7 +70,7 @@ This topic defines the terms that are used to describe the elements of XAML synt
  [!code-xaml[XAMLOvwSupport#ThisIsATextBox](~/samples/snippets/csharp/VS_Snippets_Wpf/XAMLOvwSupport/CSharp/Page1.xaml#thisisatextbox)]  
   
 ### Content Models  
- A class might support a usage as a XAML object element in terms of the syntax, but that element will only function properly in an application or page when it is placed in an expected position of an overall content model or element tree. For example, a <xref:System.Windows.Controls.MenuItem> should typically only be placed as a child of a <xref:System.Windows.Controls.Primitives.MenuBase> derived class such as <xref:System.Windows.Controls.Menu>. Content models for specific elements are documented as part of the remarks on the class pages for controls and other [!INCLUDE[TLA2#tla_winclient](../../../includes/tla2sharptla-winclient-md.md)] classes that can be used as XAML elements.  
+ A class might support a usage as a XAML object element in terms of the syntax, but that element will only function properly in an application or page when it is placed in an expected position of an overall content model or element tree. For example, a <xref:System.Windows.Controls.MenuItem> should typically only be placed as a child of a <xref:System.Windows.Controls.Primitives.MenuBase> derived class such as <xref:System.Windows.Controls.Menu>. Content models for specific elements are documented as part of the remarks on the class pages for controls and other WPF classes that can be used as XAML elements.  
   
 <a name="properties_of_object_elements"></a>
 ## Properties of Object Elements  
@@ -227,10 +228,10 @@ This topic defines the terms that are used to describe the elements of XAML synt
   
  [!code-xaml[XAMLOvwSupport#SyntaxContent](~/samples/snippets/csharp/VS_Snippets_Wpf/XAMLOvwSupport/CSharp/page5.xaml#syntaxcontent)]  
   
- Note that neither the property element for <xref:System.Windows.Controls.Panel.Children%2A> nor the element for the <xref:System.Windows.Controls.UIElementCollection> is required in the markup. This is a design feature of XAML so that recursively contained elements that define a [!INCLUDE[TLA2#tla_ui](../../../includes/tla2sharptla-ui-md.md)] are more intuitively represented as a tree of nested elements with immediate parent-child element relationships, without intervening property element tags or collection objects. In fact, <xref:System.Windows.Controls.UIElementCollection> cannot be specified explicitly in markup as an object element, by design. Because its only intended use is as an implicit collection, <xref:System.Windows.Controls.UIElementCollection> does not expose a public parameterless constructor and thus cannot be instantiated as an object element.  
+ Note that neither the property element for <xref:System.Windows.Controls.Panel.Children%2A> nor the element for the <xref:System.Windows.Controls.UIElementCollection> is required in the markup. This is a design feature of XAML so that recursively contained elements that define a UI are more intuitively represented as a tree of nested elements with immediate parent-child element relationships, without intervening property element tags or collection objects. In fact, <xref:System.Windows.Controls.UIElementCollection> cannot be specified explicitly in markup as an object element, by design. Because its only intended use is as an implicit collection, <xref:System.Windows.Controls.UIElementCollection> does not expose a public parameterless constructor and thus cannot be instantiated as an object element.  
   
 ### Mixing Property Elements and Object Elements in an Object with a Content Property  
- The XAML specification declares that a XAML processor can enforce that object elements that are used to fill the XAML content property within an object element must be contiguous, and must not be mixed. This restriction against mixing property elements and content is enforced by the [!INCLUDE[TLA2#tla_winclient](../../../includes/tla2sharptla-winclient-md.md)] XAML processors.  
+ The XAML specification declares that a XAML processor can enforce that object elements that are used to fill the XAML content property within an object element must be contiguous, and must not be mixed. This restriction against mixing property elements and content is enforced by the WPF XAML processors.  
   
  You can have a child object element as the first immediate markup within an object element. Then you can introduce property elements. Or, you can specify one or more property elements, then content, then more property elements. But once a property element follows content, you cannot introduce any further content, you can only add property elements.  
   
@@ -238,7 +239,7 @@ This topic defines the terms that are used to describe the elements of XAML synt
   
 <a name="xaml_namespaces"></a>
 ## XAML Namespaces  
- None of the preceding syntax examples specified a XAML namespace other than the default XAML namespace. In typical [!INCLUDE[TLA2#tla_winclient](../../../includes/tla2sharptla-winclient-md.md)] applications, the default XAML namespace is specified to be the [!INCLUDE[TLA2#tla_winclient](../../../includes/tla2sharptla-winclient-md.md)] namespace. You can specify XAML namespaces other than the default XAML namespace and still use similar syntax. But then, anywhere where a class is named that is not accessible within the default XAML namespace, that class name must be preceded with the prefix of the XAML namespace as mapped to the corresponding CLR namespace. For example, `<custom:Example/>` is object element syntax to instantiate an instance of the `Example` class, where the CLR namespace containing that class (and possibly the external assembly information that contains backing types) was previously mapped to the `custom` prefix.  
+ None of the preceding syntax examples specified a XAML namespace other than the default XAML namespace. In typical WPF applications, the default XAML namespace is specified to be the WPF namespace. You can specify XAML namespaces other than the default XAML namespace and still use similar syntax. But then, anywhere where a class is named that is not accessible within the default XAML namespace, that class name must be preceded with the prefix of the XAML namespace as mapped to the corresponding CLR namespace. For example, `<custom:Example/>` is object element syntax to instantiate an instance of the `Example` class, where the CLR namespace containing that class (and possibly the external assembly information that contains backing types) was previously mapped to the `custom` prefix.  
   
  For more information about XAML namespaces, see [XAML Namespaces and Namespace Mapping for WPF XAML](xaml-namespaces-and-namespace-mapping-for-wpf-xaml.md).  
   
@@ -246,7 +247,7 @@ This topic defines the terms that are used to describe the elements of XAML synt
 ## Markup Extensions  
  XAML defines a markup extension programming entity that enables an escape from the normal XAML processor handling of string attribute values or object elements, and defers the processing to a backing class. The character that identifies a markup extension to a XAML processor when using attribute syntax is the opening curly brace ({), followed by any character other than a closing curly brace (}). The first string following the opening curly brace must reference the class that provides the particular extension behavior, where the reference may omit the substring "Extension" if that substring is part of the true class name. Thereafter, a single space may appear, and then each succeeding character is used as input by the extension implementation, up until the closing curly brace is encountered.  
   
- The .NET XAML implementation uses the <xref:System.Windows.Markup.MarkupExtension> abstract class as the basis for all of the markup extensions supported by [!INCLUDE[TLA2#tla_winclient](../../../includes/tla2sharptla-winclient-md.md)] as well as other frameworks or technologies. The markup extensions that [!INCLUDE[TLA2#tla_winclient](../../../includes/tla2sharptla-winclient-md.md)] specifically implements are often intended to provide a means to reference other existing objects, or to make deferred references to objects that will be evaluated at run time. For example, a simple WPF data binding is accomplished by specifying the `{Binding}` markup extension in place of the value that a particular property would ordinarily take. Many of the WPF markup extensions enable an attribute syntax for properties where an attribute syntax would not otherwise be possible. For example, a <xref:System.Windows.Style> object is a relatively complex type that contains a nested series of objects and properties. Styles in WPF are typically defined as a resource in a <xref:System.Windows.ResourceDictionary>, and then referenced through one of the two WPF markup extensions that request a resource. The markup extension defers the evaluation of the property value to a resource lookup and enables providing the value of the <xref:System.Windows.FrameworkElement.Style%2A> property, taking type <xref:System.Windows.Style>, in attribute syntax as in the following example:  
+ The .NET XAML implementation uses the <xref:System.Windows.Markup.MarkupExtension> abstract class as the basis for all of the markup extensions supported by WPF as well as other frameworks or technologies. The markup extensions that WPF specifically implements are often intended to provide a means to reference other existing objects, or to make deferred references to objects that will be evaluated at run time. For example, a simple WPF data binding is accomplished by specifying the `{Binding}` markup extension in place of the value that a particular property would ordinarily take. Many of the WPF markup extensions enable an attribute syntax for properties where an attribute syntax would not otherwise be possible. For example, a <xref:System.Windows.Style> object is a relatively complex type that contains a nested series of objects and properties. Styles in WPF are typically defined as a resource in a <xref:System.Windows.ResourceDictionary>, and then referenced through one of the two WPF markup extensions that request a resource. The markup extension defers the evaluation of the property value to a resource lookup and enables providing the value of the <xref:System.Windows.FrameworkElement.Style%2A> property, taking type <xref:System.Windows.Style>, in attribute syntax as in the following example:  
   
  `<Button Style="{StaticResource MyStyle}">My button</Button>`  
   
@@ -275,7 +276,7 @@ This topic defines the terms that are used to describe the elements of XAML synt
 |||  
 |-|-|  
 |`<Page`|Opening object element of the root element|  
-|`xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"`|The default ([!INCLUDE[TLA2#tla_winclient](../../../includes/tla2sharptla-winclient-md.md)]) XAML namespace|  
+|`xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"`|The default (WPF) XAML namespace|  
 |`xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"`|The XAML language XAML namespace|  
 |`x:Class="ExampleNamespace.ExampleCode"`|The partial class declaration that connects markup to any code-behind defined for the partial class|  
 |`>`|End of object element for the root. Object is not closed yet because the element contains child elements|  

From 0358914363282fb51785c5cd5e7c3ffba6fa31af Mon Sep 17 00:00:00 2001
From: "Andy (Steve) De George" <67293991+adegeo@users.noreply.github.com>
Date: Mon, 24 Jan 2022 11:07:43 -0800
Subject: [PATCH 2/3] Upgrade framework winforms-outlook article (#1280)

* upgrade winforms-outlook article

* change readme name; add description

* change readme name; add description
---
 ...ipane-user-interface-with-windows-forms.md | 206 +++++-------------
 .../form.png                                  | Bin 0 -> 5509 bytes
 .../Form1.Designer.cs                         | 147 +++++++++++++
 .../Form1.cs                                  |  16 ++
 .../Form1.resx                                | 120 ++++++++++
 .../Program.cs                                |  22 ++
 .../project.csproj                            |  65 ++++++
 .../readme.txt                                |   1 +
 8 files changed, 420 insertions(+), 157 deletions(-)
 create mode 100644 dotnet-desktop-guide/framework/winforms/controls/media/how-to-create-a-multipane-user-interface-with-windows-forms/form.png
 create mode 100644 dotnet-desktop-guide/framework/winforms/controls/snippets/how-to-create-a-multipane-user-interface-with-windows-forms/Form1.Designer.cs
 create mode 100644 dotnet-desktop-guide/framework/winforms/controls/snippets/how-to-create-a-multipane-user-interface-with-windows-forms/Form1.cs
 create mode 100644 dotnet-desktop-guide/framework/winforms/controls/snippets/how-to-create-a-multipane-user-interface-with-windows-forms/Form1.resx
 create mode 100644 dotnet-desktop-guide/framework/winforms/controls/snippets/how-to-create-a-multipane-user-interface-with-windows-forms/Program.cs
 create mode 100644 dotnet-desktop-guide/framework/winforms/controls/snippets/how-to-create-a-multipane-user-interface-with-windows-forms/project.csproj
 create mode 100644 dotnet-desktop-guide/framework/winforms/controls/snippets/how-to-create-a-multipane-user-interface-with-windows-forms/readme.txt

diff --git a/dotnet-desktop-guide/framework/winforms/controls/how-to-create-a-multipane-user-interface-with-windows-forms.md b/dotnet-desktop-guide/framework/winforms/controls/how-to-create-a-multipane-user-interface-with-windows-forms.md
index 6e1039d55c..56473879e6 100644
--- a/dotnet-desktop-guide/framework/winforms/controls/how-to-create-a-multipane-user-interface-with-windows-forms.md
+++ b/dotnet-desktop-guide/framework/winforms/controls/how-to-create-a-multipane-user-interface-with-windows-forms.md
@@ -1,6 +1,7 @@
 ---
 title: Create a Multipane User Interface
-ms.date: "03/30/2017"
+description: Describes how to layout Windows Forms controls to mimic a Microsoft Outlook email application.
+ms.date: 01/21/2022
 dev_langs: 
   - "csharp"
   - "vb"
@@ -14,162 +15,53 @@ helpviewer_keywords:
 ms.assetid: e79f6bcc-3740-4d1e-b46a-c5594d9b7327
 ---
 # How to: Create a Multipane User Interface with Windows Forms
-In the following procedure, you will create a multipane user interface that is similar to the one used in Microsoft Outlook, with a **Folder** list, a **Messages** pane, and a **Preview** pane. This arrangement is achieved chiefly through docking controls with the form.  
-  
- When you dock a control, you determine which edge of the parent container a control is fastened to. Thus, if you set the <xref:System.Windows.Forms.SplitContainer.Dock%2A> property to <xref:System.Windows.Forms.DockStyle.Right>, the right edge of the control will be docked to the right edge of its parent control. Additionally, the docked edge of the control is resized to match that of its container control. For more information about how the <xref:System.Windows.Forms.SplitContainer.Dock%2A> property works, see [How to: Dock Controls on Windows Forms](how-to-dock-controls-on-windows-forms.md).  
-  
- This procedure focuses on arranging the <xref:System.Windows.Forms.SplitContainer> and the other controls on the form, not on adding functionality to make the application mimic Microsoft Outlook.  
-  
- To create this user interface, you place all the controls within a <xref:System.Windows.Forms.SplitContainer> control, which contains a <xref:System.Windows.Forms.TreeView> control in the left-hand panel. The right-hand panel of the <xref:System.Windows.Forms.SplitContainer> control contains a second <xref:System.Windows.Forms.SplitContainer> control with a <xref:System.Windows.Forms.ListView> control above a <xref:System.Windows.Forms.RichTextBox> control. These <xref:System.Windows.Forms.SplitContainer> controls enable independent resizing of the other controls on the form. You can adapt the techniques in this procedure to craft custom user interfaces of your own.  
-  
-### To create an Outlook-style user interface programmatically  
-  
-1. Within a form, declare each control that comprises your user interface. For this example, use the <xref:System.Windows.Forms.TreeView>, <xref:System.Windows.Forms.ListView>, <xref:System.Windows.Forms.SplitContainer>, and <xref:System.Windows.Forms.RichTextBox> controls to mimic the Microsoft Outlook user interface.  
-  
-    ```vb  
-    Private WithEvents treeView1 As System.Windows.Forms.TreeView  
-    Private WithEvents listView1 As System.Windows.Forms.ListView  
-    Private WithEvents richTextBox1 As System.Windows.Forms.RichTextBox  
-    Private WithEvents splitContainer1 As _  
-        System.Windows.Forms.SplitContainer  
-    Private WithEvents splitContainer2 As _  
-        System.Windows.Forms.SplitContainer  
-    ```  
-  
-    ```csharp  
-    private System.Windows.Forms.TreeView treeView1;  
-    private System.Windows.Forms.ListView listView1;  
-    private System.Windows.Forms.RichTextBox richTextBox1;  
-    private System.Windows.Forms. SplitContainer splitContainer2;  
-    private System.Windows.Forms. SplitContainer splitContainer1;  
-    ```  
-  
-2. Create a procedure that defines your user interface. The following code sets the properties so that the form will resemble the user interface in Microsoft Outlook. However, by using other controls or docking them differently, it is just as easy to create other user interfaces that are equally flexible.  
-  
-    ```vb  
-    Public Sub CreateOutlookUI()  
-        ' Create an instance of each control being used.  
-        Me.components = New System.ComponentModel.Container()  
-        Me.treeView1 = New System.Windows.Forms.TreeView()  
-        Me.listView1 = New System.Windows.Forms.ListView()  
-        Me.richTextBox1 = New System.Windows.Forms.RichTextBox()  
-        Me.splitContainer1 = New System.Windows.Forms.SplitContainer()  
-        Me.splitContainer2= New System.Windows.Forms. SplitContainer()  
-  
-        ' Should you develop this into a working application,  
-        ' use the AddHandler method to hook up event procedures here.  
-  
-        ' Set properties of TreeView control.  
-        ' Use the With statement to avoid repetitive code.  
-        With Me.treeView1  
-            .Dock = System.Windows.Forms.DockStyle.Fill  
-            .TabIndex = 0  
-            .Nodes.Add("treeView")  
-        End With  
-  
-    ' Set properties of ListView control.  
-       With Me.listView1  
-          .Dock = System.Windows.Forms.DockStyle.Top  
-          .TabIndex = 2  
-          .Items.Add("listView")  
-       End With  
-  
-    ' Set properties of RichTextBox control.  
-       With Me.richTextBox1  
-          .Dock = System.Windows.Forms.DockStyle.Fill  
-          .TabIndex = 3  
-          .Text = "richTextBox1"  
-       End With  
-  
-        ' Set properties of the first SplitContainer control.  
-        With Me.splitContainer1  
-            .Dock = System.Windows.Forms.DockStyle.Fill  
-            .TabIndex = 1  
-            .SplitterWidth = 4  
-            .SplitterDistance = 150  
-            .Orientation = Orientation.Horizontal  
-            .Panel1.Controls.Add(Me.listView1)  
-            .Panel2.Controls.Add(Me.richTextBox1)  
-    End With  
-  
-        ' Set properties of the second SplitContainer control.  
-        With Me.splitContainer2  
-            .Dock = System.Windows.Forms.DockStyle.Fill  
-            .TabIndex = 4  
-            .SplitterWidth = 4  
-            .SplitterDistance = 100  
-            .Panel1.Controls.Add(Me.treeView1)  
-            .Panel2.Controls.Add(Me.SplitContainer1)  
-    End With  
-  
-    ' Add the main SplitContainer control to the form.  
-        Me.Controls.Add(Me.splitContainer2)  
-        Me.Text = "Intricate UI Example"  
-    End Sub  
-    ```  
-  
-    ```csharp  
-    public void createOutlookUI()  
-    {  
-        // Create an instance of each control being used.  
-        treeView1 = new System.Windows.Forms.TreeView();  
-        listView1 = new System.Windows.Forms.ListView();  
-        richTextBox1 = new System.Windows.Forms.RichTextBox();  
-        splitContainer2 = new System.Windows.Forms.SplitContainer();  
-        splitContainer1 = new System.Windows.Forms.SplitContainer();  
-  
-        // Insert code here to hook up event methods.  
-  
-        // Set properties of TreeView control.  
-        treeView1.Dock = System.Windows.Forms.DockStyle.Fill;  
-        treeView1.TabIndex = 0;  
-        treeView1.Nodes.Add("treeView");  
-  
-        // Set properties of ListView control.  
-        listView1.Dock = System.Windows.Forms.DockStyle.Top;  
-        listView1.TabIndex = 2;  
-        listView1.Items.Add("listView");  
-  
-        // Set properties of RichTextBox control.  
-        richTextBox1.Dock = System.Windows.Forms.DockStyle.Fill;  
-        richTextBox1.TabIndex = 3;  
-        richTextBox1.Text = "richTextBox1";  
-  
-        // Set properties of first SplitContainer control.  
-        splitContainer1.Dock = System.Windows.Forms.DockStyle.Fill;  
-        splitContainer2.TabIndex = 1;  
-        splitContainer2.SplitterWidth = 4;  
-        splitContainer2.SplitterDistance = 150;  
-        splitContainer2.Orientation = Orientation.Horizontal;  
-        splitContainer2.Panel1.Controls.Add(this.listView1);  
-        splitContainer2.Panel1.Controls.Add(this.richTextBox1);  
-  
-        // Set properties of second SplitContainer control.  
-        splitContainer2.Dock = System.Windows.Forms.DockStyle.Fill;  
-        splitContainer2.TabIndex = 4;  
-        splitContainer2.SplitterWidth = 4;  
-        splitContainer2.SplitterDistance = 100;  
-        splitContainer2.Panel1.Controls.Add(this.treeView1);  
-        splitContainer2.Panel1.Controls.Add(this.splitContainer1);  
-  
-        // Add the main SplitContainer control to the form.  
-        this.Controls.Add(this.splitContainer2);  
-        this.Text = "Intricate UI Example";  
-    }  
-    ```  
-  
-3. In Visual Basic, add a call to the procedure you just created in the `New()` procedure. In Visual C#, add this line of code to the constructor for the form class.  
-  
-    ```vb  
-    ' Add this to the New procedure.  
-    CreateOutlookUI()  
-    ```  
-  
-    ```csharp  
-    // Add this to the form class's constructor.  
-    createOutlookUI();  
-    ```  
-  
+
+By arranging controls on a form, you can create a multi-pane user interface that's similar to the one used in Microsoft Outlook, with a **Folder** list, a **Messages** pane, and a **Preview** pane. This arrangement is achieved chiefly through docking controls with the form.
+
+When you dock a control, you determine which edge of the parent container a control is fastened to. If you set the <xref:System.Windows.Forms.SplitContainer.Dock%2A> property to <xref:System.Windows.Forms.DockStyle.Right>, the right edge of the control will be docked to the right edge of its parent control. Additionally, the docked edge of the control is resized to match that of its container control. For more information about how the <xref:System.Windows.Forms.SplitContainer.Dock%2A> property works, see [How to: Dock Controls on Windows Forms](how-to-dock-controls-on-windows-forms.md).
+
+This procedure focuses on arranging the <xref:System.Windows.Forms.SplitContainer> and the other controls on the form, not on adding functionality to make the application mimic Microsoft Outlook.
+
+:::image type="content" source="media/how-to-create-a-multipane-user-interface-with-windows-forms/form.png" alt-text="A form that's designed to look like an Outlook mail window.":::
+
+To create this user interface, you place all the controls within a <xref:System.Windows.Forms.SplitContainer> control. The `SplitContainer` contains a <xref:System.Windows.Forms.TreeView> control in the left-hand panel and another `SplitContainer` on the right-hand panel. The second `SplitContainer` contains a <xref:System.Windows.Forms.ListView> control on top and a <xref:System.Windows.Forms.RichTextBox> control on the bottom.
+
+These <xref:System.Windows.Forms.SplitContainer> controls enable independent resizing of the other controls on the form. You can adapt the techniques in this procedure to craft custom user interfaces of your own.
+
+## Control layout
+
+The following table describes how the controls are configured to mimic Microsoft Outlook:
+
+| Control        | Property         | Value                                            |
+|----------------|------------------|--------------------------------------------------|
+| SplitContainer | Name             | `splitContainer1`                                |
+|                | Dock             | `Fill`                                           |
+|                | TabIndex         | `4`                                              |
+|                | SplitterWidth    | `4`                                              |
+|                | SplitterDistance | `100`                                            |
+|                | Panel1.Controls  | Add the `treeView1` control to this panel.       |
+|                | Panel2.Controls  | Add the `splitContainer2` control to this panel. |
+| TreeView       | Name             | `treeView1`                                      |
+|                | Dock             | `Fill`                                           |
+|                | TabIndex         | `0`                                              |
+|                | Nodes            | Add a new node named `Node0`                     |
+| SplitContainer | Name             | `splitContainer2`                                |
+|                | Dock             | `Fill`                                           |
+|                | TabIndex         | `1`                                              |
+|                | SplitterWidth    | `4`                                              |
+|                | SplitterDistance | `150`                                            |
+|                | Orientation      | `Horizontal`                                     |
+|                | Panel1.Controls  | Add the `listView1` control to this panel.       |
+|                | Panel2.Controls  | Add the `richTextBox1` control to this panel.    |
+| ListView       | Name             | `listView1`                                      |
+|                | Dock             | `Fill`                                           |
+|                | TabIndex         | `2`                                              |
+|                | Items            | Add a new item and set the text to `item1`.      |
+| RichTextBox    | Name             | `richTextBox1`                                   |
+|                | Dock             | `Fill`                                           |
+|                | TabIndex         | `3`                                              |
+|                | Text             | `richTextBox1`                                   |
+
 ## See also
 
 - <xref:System.Windows.Forms.SplitContainer>
diff --git a/dotnet-desktop-guide/framework/winforms/controls/media/how-to-create-a-multipane-user-interface-with-windows-forms/form.png b/dotnet-desktop-guide/framework/winforms/controls/media/how-to-create-a-multipane-user-interface-with-windows-forms/form.png
new file mode 100644
index 0000000000000000000000000000000000000000..c916fe2fac7be9cb224322ef4945e71d2103f678
GIT binary patch
literal 5509
zcmeI0cTm$=yT^ZGUlmlOC6rxQ8%>cHL8=8o7X<`D37sIYv{0oa6m_K}B*?PTq%1^5
z2q6SXs0k>LfKnC_A}ygTMXFg!fE3>NwmW<0-nsYA>^t+`x%ZFXoH@@Q=Xd6u@ALVd
z=Sj7;G(Ykc=qmsKj@-OqY6AdbP5`j0^1wb(1eYv{5DmM+ZOpF%l|AyGM3X(fS8iVc
z08;uPzUN-i{9wopr*HreZ~gM^V!&T|1Ar9hrs);CXt$*?_dvJlxE4+k`|>rv`=<_*
zBbLszC7rS;zhnP>=rf429e($diw8&jWe&<nDmLDjJoKzw*})TZJToNh$`il$-_?8*
zQYKwi_Ug*R4>w5;ed14^dA228MuRRNP5!p+=IZPiq6Z;=OE`>8*t%w16gD4T7>?v0
zSJ}ePUWyqD8*jNEdo3+^zl37iSYs3;St;Hz*c>Z=mLaE<U=O%hLZQ%d>N^Y0ilEFY
zPPLM@J-@kDYNDX++mj}z?IUmE5R7^3A8|#yiWSEli{>rWPOTR0AYBkk<j`&%X4~4Q
z{&!XYFs_m;u7HZ;ZM3tf2pF@{^{z?Wa(EH%O!dYJ+udxir@#O<T=RYC6h=2oXCKhA
zxj6Ky^e{oW$)~qafeh7vg7(^<^Ql7Jed7$L>QvTEqUOT@fR2xD^JiccrZ0GD;UQo-
zxl}GYp*jEcaYq2iw2iRqvu$l{y|V@(M0W_b7l^f{2Y?VPsxVI{z+MhYo`fHjwrbxE
zge)7c=JvJ;1w5QR-#runTI$sr=3DOX?yHVjo!KskVmTctV)Z5nSN-8$G!6!CC%W(K
zWEr<;Pp^zfuk%tc-KO>0fjey(xb@A}30Uan4I^>kgyRR=c14F6plNW|+h~Wsy56|l
zfCuSQwXYB6!vz81<8#S(OsZ?|IIl41rHZKw(){EOu|%uK8qSoqjinJQ9@rA4JCSb?
z6|C-3R|TrqGZd`#bFwj~w%%ZL?NyYxJlDp_X0Yq(*h+jY=#s7pZ>YD#e#r`|6%L^f
z6tm3*<KSZ|L^I^(cZ&ug&l)Bp?$Ku=7re%DmWHyE@ZqWVf`gHSZVXWzxMg?Dk;_8B
zM-z4grK7aff|Z|`E`g|)SkKj&3ok6~(xhfl0WaSFpp4I{2Q^BWi7N)QK~$W?51Ubs
zIjjpX4Mv~8L+XW5I#jz*L^k)b;pfZYjogi{+6-B2c41K4=)$pA_+x;F7fP;T()A!p
zchqpeo)4w<cZa#&Xg@qyfR-*e0ma>i<Qt5sGre!0sjl2khF|9kCS_yBmp=-k*qV$D
zX>EHYp}R^|e1BR+h61KzSWYEblVUQS8_J_%a-1V9A`gq?YI&H@)uMV!q$`E8c7+}O
zN+_c`Ax#3roBntohp8J@4D~Rtkw+R$TI0mi6;g2Kz28(Pxubj;>MFs;G>U_|mNEFL
zu8Fh8mQK3+@K)b?JGu3o)NJq6@o#~Uo3dbN?tMs(wRc=dAT+IM%WM&`#U#yk)Pw~l
zs8kE5KV?s*`rf1Gm9o=ys4AGH%Q4G~_ZVmseXSRui8Y)IY(^J<w~a?rZ0*&(Iv=gJ
zgq?6ggJz}My9YSvW|X6y3$J^KGrWr7nTFD0nt1Iy>wGCd=6PRHg6~M(pKhyHgFMOH
z>1^1_U^a~1=i@!bcK}bRv6s<AVRr(Zxy&Qh;a+_#R5K|YV-$5l?d<wL7s_IXLM>kX
ztn9;5jOt=3G;-}2nBH8$G^saOXPGp&amGBD_MDRo>&a%ck{I67fK2gU{+FW<%Ra!+
zRPf0O@itn`ENV-S5^5Uj4f8+DCN(3G3ka?SX(Gz~41*deN+PXG9Jva~qP{$TNmK<<
zFp>_Nu<fP0T5;*Mh@!I$th_PEy<YfY6Zc8Cozz;}HqyNFvwTraZV@Jz18p*HpzHE&
z`152fZD*imuWggW;OmF`@wiN>X36@x8L#k$<WcQw0ar61U6z<0YfL<nyCmQUg><wM
zHhNZoBP|f9)0@AJ$)n%SR+W?Il&I3LR={z>uYkJ8C|yw8Os=nGY;a%%V!o{OZGh&*
zb}*(;))8lR4PWP@dV5}hZO%of?|g7Lv6P{Qob!`6M%EbaeEd<4(VHGG4zx^{L^HSt
zuMc{sr~~6++Qp)@_CUV)HA+Sd2)U547kGTxdl&HSQIRPeG?fM}i~T<IR#!z~a~fWL
z%@4XUE*Nm@&r{-84ethed|nsrd@|1<|Au&n_tcESE4s$L?f8v-0LXXcgx92~zk4KF
z(0@IaI=mO~P(2a1-dWfQ0;vjj0eUMvaPK1o>?4gsu=S6h&(ftUv7xoU=n>f;$mgNM
zS@idmEXR-JGSFT?&qTB3mVH8nqyGJud1+=TM%4uEeGATB7IEkGYmI*6RP6?C+!Lzc
zsi$LS*6Fa^OpAvjxC9oV52{#0C#-J6cpfnT5aQ<Y*tdE){-rj>C=4}JQ9RH`t~v>Y
zf=1p{>ajdwbQ#ShjL?6xZNc0ZpL8z}y-^?3{V<7AzeEa3E)$&^zy7=gtyVKV*($Fa
zgc`7LFf}xEG|n*jSg#?S-D?wv<aZ{|>YO{rK){wW*Tb5GzmCpzyCwblMs_~6GE1xP
z2#}o^j;gr(E(^0TRTfbZr{}d8IQWYdPB(V480(+0vfSgxrl=%Y%EO<6m)b40SZpP=
z;qu%Hic}w)4K{%|$=D$fR#S+<e!e5-Hp_agMut7I?C5|2TAoklD+hGv=}c`$`zvs)
zec|eHfrv;$ISEsDEp#Mu<oG+V#$fD1)11=k(ZTTzVNO(l_WO<jc5_Lrbg*g-9VMLP
z4Kp__cegyBexoj956w1_UmYX_7{dl)qax_2=s??WA#ARc+MUd_(s5fnF}1Yd)ymmV
zqBoJRX^lX-9_U!LVS|>mW{znbC)Y+@Xa2Y>D?5j!^bJ*b)f00vRDI;Zvk27dFbY02
z$N_PQ#d>u%_N`!JuAIgMLe4h+oB`?aS^o*0aD+hOcNV6Y55HAv2%;8f)lsH4H!1Di
zoaZB8la6$EwoKoMJpB9oIb>K&xb*Yb89d>xr+VP`XjY6wwzf;YMEGR!dOG95-gJh?
zCA`iFBa2vA&$d4$RFFUCYSYea8O&L=PWZ52DSggO>dtZ$eGmf1U*4B!!Q8@BnDGOL
zY#v!ZkKD?7nU2-zA&%Jy&MP8ZIWYr2j%SgbjT_7Z7&!~fc=c!cAm+gSqO{Zd(Y<HA
zFo(SSU~A%sO}QN3S(H;H>!V}EjOJV#!mQaB#@#h8IWE@geKH_OLpbrkfHPD-c~0G~
z6d0GB&s1=7i6(GOXCFk8ijhb0o^ORS-vBP7rqZ^=b;?}YvY#4zq+G|oLTPnz^hbx1
zaDkohh$&E~M>gb+hOh5z4Qx1WQKtuvW;a68E3tPaSndisgss;S0$nj+%9<}PKpV{D
zb&3HUUsnUbaZ&Oo?omDje0^V(|2O{d&<Cu7f&G#ga9#>UyO8-`LFGT-%>Rc(5PmtZ
zu<kDdB$ipPJ<0v&Uf3V52XZXc?TY{)UB9!F2U#>4ZTnmTRmDCY9;4GX9Xx=;!-gJm
z9n5bB#D8w}mjLvh5_g7zl+l?5s?|Uu2P`XF<#GUceB~eO7-qKLv|PV6m~;eOZUl_q
z%F=WNJ-rxo+$n!CB4Zux&M(my11zU`?45Wd2km~sDStRuc_H<5;Y%|hQIfho=*&=g
zr~PjRcfGK<&=0<nT09?8aobg+?|m4G5MUeG{_P2O_#$<<v1HcH9oYopF8F^!g-2fp
zT<E6KnNdk8`cJXs^_NUE;hdr$pGX{q2L>3FtI;QZa!=@@+V`ZgPG-i$UF+*-rPNUV
z3TM+)^;5*i>uX$M%HaIxlKxQVE~V&``|z!t0F0CXx9b3qsZyPj6SnbEt)XEUf3n{H
zg`b~ogw!jOX&YBWL=dRJB=+P*teZ2|q1D$$y&uC0i0FjdGINL!^+ObM-rrE$-~A#e
zR)?aQBN@~#Jjhjdr{Cn({OLf;hht8+M!#T>xqvg?j8;FhKdHpGb26pp^~{B_@wX}M
z7A2)QSN&ah--QNgv2;x+mHH#UxrP#1Ij?BY-<;hwwjwJqw5>7HGhf@7_;~k(H6k1-
z5b<@K;nP3ZK6zmdG%`t#R6~ci8#SufUvy`C%nmxbd|=(=x_~7eEA}L69~bT5K~G&N
ztV?;~7y2BAF;y%z;22<DLEth_USE}kE?vVhDc#@48)i<r?cUutX8*{>S<86<3<lpF
zBvH=IM4iJfZ>deKr3YhTP6bqHQ#6-Rw{b*btO9`>L4QCXW|4Gh2(gy7RCUd(u&ZUG
zpx5?meZSyIWIflt@14jj$$~=^I^H+-Oh5^DPhzM@HI2$XB?gM%xaJ=ww<@wWX2K>+
zpLo`2UX*WU&auA^)KuwN0jJTns3dR0m2T@ERCoG_emT>@==8-JlJ344w!Mam<>x}+
zyrnYw>@Og-LGJZ63d915SKc1f%|3K`@dt!P%t?JFF~#f%#3Gi^N4j^nYsKxjQK++=
zRge<GBd$x^DG1l=B*jG<dO=nT|7v!)K6q(eX^)r(YIE#Se%p%Xp2SX0<Dp%^kEy>y
zfwdYd`GANKw*UJW@x_0x5Zs6kjR0`#Q3>()sQ7m;&woKj_y?c8PW^YC)B`02-_ZQ0
zIPl+z`+vZ4|6WIw=ZGFO|AW`d3r7w(@?TI$|5>&52W|Bwxu(YMZ#nkm==Aser38aC
zPNLK%%Rd#BCjo$-3~yrztwwCR;P2oX2~nx8tVj~oW-`~krQ#q@wP0plb#HG;11)x&
z;}0cD=J3OjOjnsA>T+K63YA-KD@tIxsOvN(>M*4S5UG@Um(A1e+fyG&F!M+dkeI5f
zc#lmEaJYnqtU=x_5S!ghV%Plm8@0_E_=OiwgHhn%y5ffXcYWpN4vgykD@1JG#lVk8
z(b5{_SRj#vnyo@XUSCTVf1&~5x4+3MFo?>^fCM&1t!S3kvEtxX^0JpssO;Z4nw&0A
zFfMr4nVJDnSKAFJ$%*=CMu?5J&!0n@wq~Ach0k>5h&pDso?ax3LRryMm~9e_@wP+N
zSkW-L3h9C0Z1XY*`}IZ)t}Nb!(8*ds(umA0J~VTp_d(eV54qg*diD9V&1SsoB9Vin
z(K_P^W$~DH0g4d)G|9{9^E{rY>9D)hsz{LxB^<7R5~Oz|8n<d_Px5k3iCU+?&Fhw?
Jl~+9;{27E039A4A

literal 0
HcmV?d00001

diff --git a/dotnet-desktop-guide/framework/winforms/controls/snippets/how-to-create-a-multipane-user-interface-with-windows-forms/Form1.Designer.cs b/dotnet-desktop-guide/framework/winforms/controls/snippets/how-to-create-a-multipane-user-interface-with-windows-forms/Form1.Designer.cs
new file mode 100644
index 0000000000..a3d83e84ef
--- /dev/null
+++ b/dotnet-desktop-guide/framework/winforms/controls/snippets/how-to-create-a-multipane-user-interface-with-windows-forms/Form1.Designer.cs
@@ -0,0 +1,147 @@
+
+namespace project
+{
+    partial class Form1
+    {
+        /// <summary>
+        /// Required designer variable.
+        /// </summary>
+        private System.ComponentModel.IContainer components = null;
+
+        /// <summary>
+        /// Clean up any resources being used.
+        /// </summary>
+        /// <param name="disposing">true if managed resources should be disposed; otherwise, false.</param>
+        protected override void Dispose(bool disposing)
+        {
+            if (disposing && (components != null))
+            {
+                components.Dispose();
+            }
+            base.Dispose(disposing);
+        }
+
+        #region Windows Form Designer generated code
+
+        /// <summary>
+        /// Required method for Designer support - do not modify
+        /// the contents of this method with the code editor.
+        /// </summary>
+        private void InitializeComponent()
+        {
+            System.Windows.Forms.TreeNode treeNode1 = new System.Windows.Forms.TreeNode("Node0");
+            System.Windows.Forms.ListViewItem listViewItem1 = new System.Windows.Forms.ListViewItem("item1");
+            this.splitContainer1 = new System.Windows.Forms.SplitContainer();
+            this.treeView1 = new System.Windows.Forms.TreeView();
+            this.splitContainer2 = new System.Windows.Forms.SplitContainer();
+            this.listView1 = new System.Windows.Forms.ListView();
+            this.richTextBox1 = new System.Windows.Forms.RichTextBox();
+            ((System.ComponentModel.ISupportInitialize)(this.splitContainer1)).BeginInit();
+            this.splitContainer1.Panel1.SuspendLayout();
+            this.splitContainer1.Panel2.SuspendLayout();
+            this.splitContainer1.SuspendLayout();
+            ((System.ComponentModel.ISupportInitialize)(this.splitContainer2)).BeginInit();
+            this.splitContainer2.Panel1.SuspendLayout();
+            this.splitContainer2.Panel2.SuspendLayout();
+            this.splitContainer2.SuspendLayout();
+            this.SuspendLayout();
+            // 
+            // splitContainer1
+            // 
+            this.splitContainer1.Dock = System.Windows.Forms.DockStyle.Fill;
+            this.splitContainer1.Location = new System.Drawing.Point(0, 0);
+            this.splitContainer1.Name = "splitContainer1";
+            // 
+            // splitContainer1.Panel1
+            // 
+            this.splitContainer1.Panel1.Controls.Add(this.treeView1);
+            // 
+            // splitContainer1.Panel2
+            // 
+            this.splitContainer1.Panel2.Controls.Add(this.splitContainer2);
+            this.splitContainer1.Size = new System.Drawing.Size(448, 366);
+            this.splitContainer1.SplitterDistance = 100;
+            this.splitContainer1.TabIndex = 1;
+            // 
+            // treeView1
+            // 
+            this.treeView1.Dock = System.Windows.Forms.DockStyle.Fill;
+            this.treeView1.Location = new System.Drawing.Point(0, 0);
+            this.treeView1.Name = "treeView1";
+            treeNode1.Name = "Node0";
+            treeNode1.Text = "Node0";
+            this.treeView1.Nodes.AddRange(new System.Windows.Forms.TreeNode[] {
+            treeNode1});
+            this.treeView1.Size = new System.Drawing.Size(100, 366);
+            this.treeView1.TabIndex = 0;
+            // 
+            // splitContainer2
+            // 
+            this.splitContainer2.Dock = System.Windows.Forms.DockStyle.Fill;
+            this.splitContainer2.Location = new System.Drawing.Point(0, 0);
+            this.splitContainer2.Name = "splitContainer2";
+            this.splitContainer2.Orientation = System.Windows.Forms.Orientation.Horizontal;
+            // 
+            // splitContainer2.Panel1
+            // 
+            this.splitContainer2.Panel1.Controls.Add(this.listView1);
+            // 
+            // splitContainer2.Panel2
+            // 
+            this.splitContainer2.Panel2.Controls.Add(this.richTextBox1);
+            this.splitContainer2.Size = new System.Drawing.Size(344, 366);
+            this.splitContainer2.SplitterDistance = 156;
+            this.splitContainer2.TabIndex = 1;
+            // 
+            // listView1
+            // 
+            this.listView1.Dock = System.Windows.Forms.DockStyle.Fill;
+            this.listView1.HideSelection = false;
+            this.listView1.Items.AddRange(new System.Windows.Forms.ListViewItem[] {
+            listViewItem1});
+            this.listView1.Location = new System.Drawing.Point(0, 0);
+            this.listView1.Name = "listView1";
+            this.listView1.Size = new System.Drawing.Size(344, 156);
+            this.listView1.TabIndex = 2;
+            this.listView1.UseCompatibleStateImageBehavior = false;
+            // 
+            // richTextBox1
+            // 
+            this.richTextBox1.Dock = System.Windows.Forms.DockStyle.Fill;
+            this.richTextBox1.Location = new System.Drawing.Point(0, 0);
+            this.richTextBox1.Name = "richTextBox1";
+            this.richTextBox1.Size = new System.Drawing.Size(344, 206);
+            this.richTextBox1.TabIndex = 3;
+            this.richTextBox1.Text = "richTextBox1";
+            // 
+            // Form1
+            // 
+            this.AutoScaleDimensions = new System.Drawing.SizeF(6F, 13F);
+            this.AutoScaleMode = System.Windows.Forms.AutoScaleMode.Font;
+            this.ClientSize = new System.Drawing.Size(448, 366);
+            this.Controls.Add(this.splitContainer1);
+            this.Margin = new System.Windows.Forms.Padding(2);
+            this.Name = "Form1";
+            this.Text = "Form1";
+            this.splitContainer1.Panel1.ResumeLayout(false);
+            this.splitContainer1.Panel2.ResumeLayout(false);
+            ((System.ComponentModel.ISupportInitialize)(this.splitContainer1)).EndInit();
+            this.splitContainer1.ResumeLayout(false);
+            this.splitContainer2.Panel1.ResumeLayout(false);
+            this.splitContainer2.Panel2.ResumeLayout(false);
+            ((System.ComponentModel.ISupportInitialize)(this.splitContainer2)).EndInit();
+            this.splitContainer2.ResumeLayout(false);
+            this.ResumeLayout(false);
+
+        }
+
+        #endregion
+
+        private System.Windows.Forms.SplitContainer splitContainer1;
+        private System.Windows.Forms.TreeView treeView1;
+        private System.Windows.Forms.SplitContainer splitContainer2;
+        private System.Windows.Forms.ListView listView1;
+        private System.Windows.Forms.RichTextBox richTextBox1;
+    }
+}
+
diff --git a/dotnet-desktop-guide/framework/winforms/controls/snippets/how-to-create-a-multipane-user-interface-with-windows-forms/Form1.cs b/dotnet-desktop-guide/framework/winforms/controls/snippets/how-to-create-a-multipane-user-interface-with-windows-forms/Form1.cs
new file mode 100644
index 0000000000..a7cac9af99
--- /dev/null
+++ b/dotnet-desktop-guide/framework/winforms/controls/snippets/how-to-create-a-multipane-user-interface-with-windows-forms/Form1.cs
@@ -0,0 +1,16 @@
+using System;
+using System.Collections;
+using System.Collections.Generic;
+using System.Windows.Forms;
+
+namespace project
+{
+    public partial class Form1 : Form
+    {
+        //Windows Form application
+        public Form1()
+        {
+            InitializeComponent();
+        }
+    }
+}
diff --git a/dotnet-desktop-guide/framework/winforms/controls/snippets/how-to-create-a-multipane-user-interface-with-windows-forms/Form1.resx b/dotnet-desktop-guide/framework/winforms/controls/snippets/how-to-create-a-multipane-user-interface-with-windows-forms/Form1.resx
new file mode 100644
index 0000000000..1af7de150c
--- /dev/null
+++ b/dotnet-desktop-guide/framework/winforms/controls/snippets/how-to-create-a-multipane-user-interface-with-windows-forms/Form1.resx
@@ -0,0 +1,120 @@
+<?xml version="1.0" encoding="utf-8"?>
+<root>
+  <!-- 
+    Microsoft ResX Schema 
+    
+    Version 2.0
+    
+    The primary goals of this format is to allow a simple XML format 
+    that is mostly human readable. The generation and parsing of the 
+    various data types are done through the TypeConverter classes 
+    associated with the data types.
+    
+    Example:
+    
+    ... ado.net/XML headers & schema ...
+    <resheader name="resmimetype">text/microsoft-resx</resheader>
+    <resheader name="version">2.0</resheader>
+    <resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader>
+    <resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader>
+    <data name="Name1"><value>this is my long string</value><comment>this is a comment</comment></data>
+    <data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data>
+    <data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64">
+        <value>[base64 mime encoded serialized .NET Framework object]</value>
+    </data>
+    <data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64">
+        <value>[base64 mime encoded string representing a byte array form of the .NET Framework object]</value>
+        <comment>This is a comment</comment>
+    </data>
+                
+    There are any number of "resheader" rows that contain simple 
+    name/value pairs.
+    
+    Each data row contains a name, and value. The row also contains a 
+    type or mimetype. Type corresponds to a .NET class that support 
+    text/value conversion through the TypeConverter architecture. 
+    Classes that don't support this are serialized and stored with the 
+    mimetype set.
+    
+    The mimetype is used for serialized objects, and tells the 
+    ResXResourceReader how to depersist the object. This is currently not 
+    extensible. For a given mimetype the value must be set accordingly:
+    
+    Note - application/x-microsoft.net.object.binary.base64 is the format 
+    that the ResXResourceWriter will generate, however the reader can 
+    read any of the formats listed below.
+    
+    mimetype: application/x-microsoft.net.object.binary.base64
+    value   : The object must be serialized with 
+            : System.Runtime.Serialization.Formatters.Binary.BinaryFormatter
+            : and then encoded with base64 encoding.
+    
+    mimetype: application/x-microsoft.net.object.soap.base64
+    value   : The object must be serialized with 
+            : System.Runtime.Serialization.Formatters.Soap.SoapFormatter
+            : and then encoded with base64 encoding.
+
+    mimetype: application/x-microsoft.net.object.bytearray.base64
+    value   : The object must be serialized into a byte array 
+            : using a System.ComponentModel.TypeConverter
+            : and then encoded with base64 encoding.
+    -->
+  <xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
+    <xsd:import namespace="http://www.w3.org/XML/1998/namespace" />
+    <xsd:element name="root" msdata:IsDataSet="true">
+      <xsd:complexType>
+        <xsd:choice maxOccurs="unbounded">
+          <xsd:element name="metadata">
+            <xsd:complexType>
+              <xsd:sequence>
+                <xsd:element name="value" type="xsd:string" minOccurs="0" />
+              </xsd:sequence>
+              <xsd:attribute name="name" use="required" type="xsd:string" />
+              <xsd:attribute name="type" type="xsd:string" />
+              <xsd:attribute name="mimetype" type="xsd:string" />
+              <xsd:attribute ref="xml:space" />
+            </xsd:complexType>
+          </xsd:element>
+          <xsd:element name="assembly">
+            <xsd:complexType>
+              <xsd:attribute name="alias" type="xsd:string" />
+              <xsd:attribute name="name" type="xsd:string" />
+            </xsd:complexType>
+          </xsd:element>
+          <xsd:element name="data">
+            <xsd:complexType>
+              <xsd:sequence>
+                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
+                <xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" />
+              </xsd:sequence>
+              <xsd:attribute name="name" type="xsd:string" use="required" msdata:Ordinal="1" />
+              <xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" />
+              <xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" />
+              <xsd:attribute ref="xml:space" />
+            </xsd:complexType>
+          </xsd:element>
+          <xsd:element name="resheader">
+            <xsd:complexType>
+              <xsd:sequence>
+                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
+              </xsd:sequence>
+              <xsd:attribute name="name" type="xsd:string" use="required" />
+            </xsd:complexType>
+          </xsd:element>
+        </xsd:choice>
+      </xsd:complexType>
+    </xsd:element>
+  </xsd:schema>
+  <resheader name="resmimetype">
+    <value>text/microsoft-resx</value>
+  </resheader>
+  <resheader name="version">
+    <value>2.0</value>
+  </resheader>
+  <resheader name="reader">
+    <value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
+  </resheader>
+  <resheader name="writer">
+    <value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
+  </resheader>
+</root>
\ No newline at end of file
diff --git a/dotnet-desktop-guide/framework/winforms/controls/snippets/how-to-create-a-multipane-user-interface-with-windows-forms/Program.cs b/dotnet-desktop-guide/framework/winforms/controls/snippets/how-to-create-a-multipane-user-interface-with-windows-forms/Program.cs
new file mode 100644
index 0000000000..b7580e129c
--- /dev/null
+++ b/dotnet-desktop-guide/framework/winforms/controls/snippets/how-to-create-a-multipane-user-interface-with-windows-forms/Program.cs
@@ -0,0 +1,22 @@
+using System;
+using System.Collections.Generic;
+using System.Linq;
+using System.Threading.Tasks;
+using System.Windows.Forms;
+
+namespace project
+{
+    static class Program
+    {
+        /// <summary>
+        /// The main entry point for the application.
+        /// </summary>
+        [STAThread]
+        static void Main()
+        {
+            Application.EnableVisualStyles();
+            Application.SetCompatibleTextRenderingDefault(false);
+            Application.Run(new Form1());
+        }
+    }
+}
diff --git a/dotnet-desktop-guide/framework/winforms/controls/snippets/how-to-create-a-multipane-user-interface-with-windows-forms/project.csproj b/dotnet-desktop-guide/framework/winforms/controls/snippets/how-to-create-a-multipane-user-interface-with-windows-forms/project.csproj
new file mode 100644
index 0000000000..1c2538b11f
--- /dev/null
+++ b/dotnet-desktop-guide/framework/winforms/controls/snippets/how-to-create-a-multipane-user-interface-with-windows-forms/project.csproj
@@ -0,0 +1,65 @@
+<?xml version="1.0" encoding="utf-8"?>
+<Project ToolsVersion="15.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
+  <Import Project="$(MSBuildExtensionsPath)\$(MSBuildToolsVersion)\Microsoft.Common.props" Condition="Exists('$(MSBuildExtensionsPath)\$(MSBuildToolsVersion)\Microsoft.Common.props')" />
+  <PropertyGroup>
+    <Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration>
+    <Platform Condition=" '$(Platform)' == '' ">AnyCPU</Platform>
+    <ProjectGuid>{50B5AD53-1181-46C6-91EE-0E65BADF34E1}</ProjectGuid>
+    <OutputType>WinExe</OutputType>
+    <RootNamespace>project</RootNamespace>
+    <AssemblyName>project</AssemblyName>
+    <TargetFrameworkVersion>v4.8</TargetFrameworkVersion>
+    <FileAlignment>512</FileAlignment>
+    <AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects>
+    <Deterministic>true</Deterministic>
+  </PropertyGroup>
+  <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' ">
+    <PlatformTarget>AnyCPU</PlatformTarget>
+    <DebugSymbols>true</DebugSymbols>
+    <DebugType>full</DebugType>
+    <Optimize>false</Optimize>
+    <OutputPath>bin\Debug\</OutputPath>
+    <DefineConstants>DEBUG;TRACE</DefineConstants>
+    <ErrorReport>prompt</ErrorReport>
+    <WarningLevel>4</WarningLevel>
+  </PropertyGroup>
+  <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' ">
+    <PlatformTarget>AnyCPU</PlatformTarget>
+    <DebugType>pdbonly</DebugType>
+    <Optimize>true</Optimize>
+    <OutputPath>bin\Release\</OutputPath>
+    <DefineConstants>TRACE</DefineConstants>
+    <ErrorReport>prompt</ErrorReport>
+    <WarningLevel>4</WarningLevel>
+  </PropertyGroup>
+  <PropertyGroup>
+    <GenerateResourceMSBuildArchitecture>CurrentArchitecture</GenerateResourceMSBuildArchitecture>
+    <GenerateResourceMSBuildRuntime>CurrentRuntime</GenerateResourceMSBuildRuntime>
+  </PropertyGroup>
+  <ItemGroup>
+    <Reference Include="System" />
+    <Reference Include="System.Core" />
+    <Reference Include="System.Xml.Linq" />
+    <Reference Include="System.Data.DataSetExtensions" />
+    <Reference Include="Microsoft.CSharp" />
+    <Reference Include="System.Data" />
+    <Reference Include="System.Deployment" />
+    <Reference Include="System.Drawing" />
+    <Reference Include="System.Net.Http" />
+    <Reference Include="System.Windows.Forms" />
+    <Reference Include="System.Xml" />
+  </ItemGroup>
+  <ItemGroup>
+    <Compile Include="Form1.cs">
+      <SubType>Form</SubType>
+    </Compile>
+    <Compile Include="Form1.Designer.cs">
+      <DependentUpon>Form1.cs</DependentUpon>
+    </Compile>
+    <Compile Include="Program.cs" />
+    <EmbeddedResource Include="Form1.resx">
+      <DependentUpon>Form1.cs</DependentUpon>
+    </EmbeddedResource>
+  </ItemGroup>
+  <Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" />
+</Project>
\ No newline at end of file
diff --git a/dotnet-desktop-guide/framework/winforms/controls/snippets/how-to-create-a-multipane-user-interface-with-windows-forms/readme.txt b/dotnet-desktop-guide/framework/winforms/controls/snippets/how-to-create-a-multipane-user-interface-with-windows-forms/readme.txt
new file mode 100644
index 0000000000..47cb859fbb
--- /dev/null
+++ b/dotnet-desktop-guide/framework/winforms/controls/snippets/how-to-create-a-multipane-user-interface-with-windows-forms/readme.txt
@@ -0,0 +1 @@
+This code is used to generate the screenshot referenced in the parent article.

From a5e3c44dcb224c8e8991bfb0618fb12d09955ab5 Mon Sep 17 00:00:00 2001
From: "Andy (Steve) De George" <67293991+adegeo@users.noreply.github.com>
Date: Mon, 24 Jan 2022 11:08:12 -0800
Subject: [PATCH 3/3] Migrate code;widen xaml snip ref (#1279)

---
 ...s-by-using-columndefinitionscollections.md |  6 +--
 .../csharp/Window1.xaml                       | 54 +++++++++++++++++++
 .../csharp}/Window1.xaml.cs                   |  0
 .../csharp/app.config                         |  3 ++
 .../csharp}/app.xaml                          |  0
 .../csharp}/app.xaml.cs                       |  0
 .../csharp}/columndefinitions_grid.csproj     | 14 +++--
 .../csharp/snippets.5000.json                 |  3 ++
 .../vb}/ColumnDefinitionsGrid.vbproj          | 14 +++--
 .../vb}/Window1.xaml                          |  0
 .../vb}/Window1.xaml.vb                       |  0
 .../vb/app.config                             | 23 ++++++++
 .../vb}/app.xaml                              |  0
 .../vb/snippets.5000.json                     |  3 ++
 .../ColumnDefinitionsGrid/CSharp/Window1.xaml | 54 -------------------
 15 files changed, 111 insertions(+), 63 deletions(-)
 create mode 100644 dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/csharp/Window1.xaml
 rename dotnet-desktop-guide/{samples/snippets/csharp/VS_Snippets_Wpf/ColumnDefinitionsGrid/CSharp => framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/csharp}/Window1.xaml.cs (100%)
 create mode 100644 dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/csharp/app.config
 rename dotnet-desktop-guide/{samples/snippets/csharp/VS_Snippets_Wpf/ColumnDefinitionsGrid/CSharp => framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/csharp}/app.xaml (100%)
 rename dotnet-desktop-guide/{samples/snippets/csharp/VS_Snippets_Wpf/ColumnDefinitionsGrid/CSharp => framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/csharp}/app.xaml.cs (100%)
 rename dotnet-desktop-guide/{samples/snippets/csharp/VS_Snippets_Wpf/ColumnDefinitionsGrid/CSharp => framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/csharp}/columndefinitions_grid.csproj (76%)
 create mode 100644 dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/csharp/snippets.5000.json
 rename dotnet-desktop-guide/{samples/snippets/visualbasic/VS_Snippets_Wpf/ColumnDefinitionsGrid/VisualBasic => framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/vb}/ColumnDefinitionsGrid.vbproj (74%)
 rename dotnet-desktop-guide/{samples/snippets/visualbasic/VS_Snippets_Wpf/ColumnDefinitionsGrid/VisualBasic => framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/vb}/Window1.xaml (100%)
 rename dotnet-desktop-guide/{samples/snippets/visualbasic/VS_Snippets_Wpf/ColumnDefinitionsGrid/VisualBasic => framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/vb}/Window1.xaml.vb (100%)
 create mode 100644 dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/vb/app.config
 rename dotnet-desktop-guide/{samples/snippets/visualbasic/VS_Snippets_Wpf/ColumnDefinitionsGrid/VisualBasic => framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/vb}/app.xaml (100%)
 create mode 100644 dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/vb/snippets.5000.json
 delete mode 100644 dotnet-desktop-guide/samples/snippets/csharp/VS_Snippets_Wpf/ColumnDefinitionsGrid/CSharp/Window1.xaml

diff --git a/dotnet-desktop-guide/framework/wpf/controls/manipulate-columns-and-rows-by-using-columndefinitionscollections.md b/dotnet-desktop-guide/framework/wpf/controls/manipulate-columns-and-rows-by-using-columndefinitionscollections.md
index 16d6f1877d..3f0b2ac5ed 100644
--- a/dotnet-desktop-guide/framework/wpf/controls/manipulate-columns-and-rows-by-using-columndefinitionscollections.md
+++ b/dotnet-desktop-guide/framework/wpf/controls/manipulate-columns-and-rows-by-using-columndefinitionscollections.md
@@ -16,12 +16,12 @@ This example shows how to use the methods in the <xref:System.Windows.Controls.C
 ## Example  
  The following example creates a <xref:System.Windows.Controls.Grid> element with a <xref:System.Windows.FrameworkElement.Name%2A> of `grid1`. The <xref:System.Windows.Controls.Grid> contains a <xref:System.Windows.Controls.StackPanel> that holds <xref:System.Windows.Controls.Button> elements, each controlled by a different collection method. When you click a <xref:System.Windows.Controls.Button>, it activates a method call in the code-behind file.  
   
- [!code-xaml[ColumnDefinitionsGrid#1](~/samples/snippets/csharp/VS_Snippets_Wpf/ColumnDefinitionsGrid/CSharp/Window1.xaml#1)]  
+:::code language="xaml" source="snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/csharp/Window1.xaml" id="Snippet1":::
   
  This example defines a series of custom methods, each corresponding to a <xref:System.Windows.Controls.Primitives.ButtonBase.Click> event in the [!INCLUDE[TLA#tla_xaml](../../../includes/tlasharptla-xaml-md.md)] file. You can change the number of columns and rows in the <xref:System.Windows.Controls.Grid> in several ways, which includes adding or removing rows and columns; and counting the total number of rows and columns. To prevent <xref:System.ArgumentOutOfRangeException> and <xref:System.ArgumentException> exceptions, you can use the error-checking functionality that the <xref:System.Windows.Controls.ColumnDefinitionCollection.RemoveRange%2A> method provides.  
   
- [!code-csharp[ColumnDefinitionsGrid#2](~/samples/snippets/csharp/VS_Snippets_Wpf/ColumnDefinitionsGrid/CSharp/Window1.xaml.cs#2)]
- [!code-vb[ColumnDefinitionsGrid#2](~/samples/snippets/visualbasic/VS_Snippets_Wpf/ColumnDefinitionsGrid/VisualBasic/Window1.xaml.vb#2)]  
+:::code language="csharp" source="snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/csharp/Window1.xaml.cs" id="Snippet2":::
+:::code language="vb" source="snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/vb/Window1.xaml.vb" id="Snippet2":::
   
 ## See also
 
diff --git a/dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/csharp/Window1.xaml b/dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/csharp/Window1.xaml
new file mode 100644
index 0000000000..1c7b6bfac2
--- /dev/null
+++ b/dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/csharp/Window1.xaml
@@ -0,0 +1,54 @@
+<Window  
+    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
+    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
+    x:Class="columndefinitions_grid.Window1"
+    Title="ColumnDefinitions Sample">
+    <Border BorderBrush="Black" Background="White" BorderThickness="2">
+        <!-- <Snippet1> -->
+        <DockPanel Margin="10,0,0,0">
+
+            <TextBlock FontSize="20" FontWeight="Bold" DockPanel.Dock="Top">Grid Column and Row Collections</TextBlock>
+            <TextBlock DockPanel.Dock="Top">Click any of the buttons below to invoke the associated methods and properties of ColumnDefinition and RowDefinition Collections.</TextBlock>
+            <Grid DockPanel.Dock="Top" HorizontalAlignment="Left" Name="grid1" ShowGridLines="true" Width="625" Height="400" Background="#b0e0e6">
+                <Grid.ColumnDefinitions>
+                    <ColumnDefinition/>
+                    <ColumnDefinition/>
+                    <ColumnDefinition/>
+                </Grid.ColumnDefinitions>
+                <Grid.RowDefinitions>
+                    <RowDefinition/>
+                    <RowDefinition/>
+                    <RowDefinition/>
+                </Grid.RowDefinitions>
+            </Grid>
+
+            <StackPanel HorizontalAlignment="Left" Orientation="Horizontal" Width="625" DockPanel.Dock="Top">
+                <Button Width="125" Click="addCol">Add Column</Button>
+                <Button Width="125" Click="addRow">Add Row</Button>
+                <Button Width="125" Click="clearCol">Clear All Columns</Button>
+                <Button Width="125" Click="clearRow">Clear All Rows</Button>
+                <Button Width="125" Click="removeCol">Remove One Column</Button>
+            </StackPanel>
+            <StackPanel HorizontalAlignment="Left" Orientation="Horizontal" Width="625" DockPanel.Dock="Top">
+                <Button Width="125" Click="removeRow">Remove One Row</Button>
+                <Button Width="125" Click="colCount">How Many Columns?</Button>
+                <Button Width="125" Click="rowCount">How Many Rows?</Button>
+                <Button Width="125" Click="rem5Col">Remove 5 Columns</Button>
+                <Button Width="125" Click="rem5Row">Remove 5 Rows</Button>
+            </StackPanel>
+            <StackPanel HorizontalAlignment="Left" Orientation="Horizontal" Width="625" DockPanel.Dock="Top">
+                <Button Width="125" Click="containsRow">Contains Row?</Button>
+                <Button Width="125" Click="containsCol">Contains Column?</Button>
+                <Button Width="125" Click="insertRowAt">Insert Row</Button>
+                <Button Width="125" Click="insertColAt">Insert Column</Button>
+                <Button Width="125" Click="colReadOnly">IsReadOnly?</Button>
+            </StackPanel>
+            <TextBlock DockPanel.Dock="Top" Name="tp1"/>
+            <TextBlock DockPanel.Dock="Top" Name="tp2"/>
+            <TextBlock DockPanel.Dock="Top" Name="tp3"/>
+            <TextBlock DockPanel.Dock="Top" Name="tp4"/>
+            <TextBlock DockPanel.Dock="Top" Name="tp5"/>
+        </DockPanel>
+        <!-- </Snippet1> -->
+    </Border>
+</Window>
diff --git a/dotnet-desktop-guide/samples/snippets/csharp/VS_Snippets_Wpf/ColumnDefinitionsGrid/CSharp/Window1.xaml.cs b/dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/csharp/Window1.xaml.cs
similarity index 100%
rename from dotnet-desktop-guide/samples/snippets/csharp/VS_Snippets_Wpf/ColumnDefinitionsGrid/CSharp/Window1.xaml.cs
rename to dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/csharp/Window1.xaml.cs
diff --git a/dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/csharp/app.config b/dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/csharp/app.config
new file mode 100644
index 0000000000..3e0e37cfc8
--- /dev/null
+++ b/dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/csharp/app.config
@@ -0,0 +1,3 @@
+<?xml version="1.0" encoding="utf-8"?>
+<configuration>
+<startup><supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.8"/></startup></configuration>
diff --git a/dotnet-desktop-guide/samples/snippets/csharp/VS_Snippets_Wpf/ColumnDefinitionsGrid/CSharp/app.xaml b/dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/csharp/app.xaml
similarity index 100%
rename from dotnet-desktop-guide/samples/snippets/csharp/VS_Snippets_Wpf/ColumnDefinitionsGrid/CSharp/app.xaml
rename to dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/csharp/app.xaml
diff --git a/dotnet-desktop-guide/samples/snippets/csharp/VS_Snippets_Wpf/ColumnDefinitionsGrid/CSharp/app.xaml.cs b/dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/csharp/app.xaml.cs
similarity index 100%
rename from dotnet-desktop-guide/samples/snippets/csharp/VS_Snippets_Wpf/ColumnDefinitionsGrid/CSharp/app.xaml.cs
rename to dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/csharp/app.xaml.cs
diff --git a/dotnet-desktop-guide/samples/snippets/csharp/VS_Snippets_Wpf/ColumnDefinitionsGrid/CSharp/columndefinitions_grid.csproj b/dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/csharp/columndefinitions_grid.csproj
similarity index 76%
rename from dotnet-desktop-guide/samples/snippets/csharp/VS_Snippets_Wpf/ColumnDefinitionsGrid/CSharp/columndefinitions_grid.csproj
rename to dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/csharp/columndefinitions_grid.csproj
index 925a490e5f..5ad2143bbe 100644
--- a/dotnet-desktop-guide/samples/snippets/csharp/VS_Snippets_Wpf/ColumnDefinitionsGrid/CSharp/columndefinitions_grid.csproj
+++ b/dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/csharp/columndefinitions_grid.csproj
@@ -1,14 +1,19 @@
-<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003" ToolsVersion="4.0">
+<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003" ToolsVersion="12.0">
   <PropertyGroup>
     <AssemblyName>SDKSample</AssemblyName>
     <TargetType>winexe</TargetType>
     <Configuration Condition="'$(Configuration)'==''">Debug</Configuration>
     <SchemaVersion>2.0</SchemaVersion>
     <OutputPath>bin\$(Configuration)\</OutputPath>
-    <TargetFrameworkVersion>v4.0</TargetFrameworkVersion>
+    <TargetFrameworkVersion>v4.8</TargetFrameworkVersion>
     <ProjectTypeGuids>{60dc8134-eba5-43b8-bcc9-bb4bc16c2548};{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}</ProjectTypeGuids>
-    <TargetFrameworkProfile>Client</TargetFrameworkProfile>
+    <TargetFrameworkProfile>
+    </TargetFrameworkProfile>
     <ProductVersion>10.0.20821</ProductVersion>
+    <ProjectGuid>{4BDD3A99-C878-405A-9108-7C948EA50659}</ProjectGuid>
+  </PropertyGroup>
+  <PropertyGroup Condition="'$(Configuration)|$(Platform)' == 'Debug|x86'">
+    <Prefer32Bit>false</Prefer32Bit>
   </PropertyGroup>
   <Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" />
   <ItemGroup>
@@ -44,4 +49,7 @@
       <SubType>Code</SubType>
     </Compile>
   </ItemGroup>
+  <ItemGroup>
+    <None Include="app.config" />
+  </ItemGroup>
 </Project>
\ No newline at end of file
diff --git a/dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/csharp/snippets.5000.json b/dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/csharp/snippets.5000.json
new file mode 100644
index 0000000000..9493e73361
--- /dev/null
+++ b/dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/csharp/snippets.5000.json
@@ -0,0 +1,3 @@
+{
+    "host": "visualstudio"
+}
\ No newline at end of file
diff --git a/dotnet-desktop-guide/samples/snippets/visualbasic/VS_Snippets_Wpf/ColumnDefinitionsGrid/VisualBasic/ColumnDefinitionsGrid.vbproj b/dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/vb/ColumnDefinitionsGrid.vbproj
similarity index 74%
rename from dotnet-desktop-guide/samples/snippets/visualbasic/VS_Snippets_Wpf/ColumnDefinitionsGrid/VisualBasic/ColumnDefinitionsGrid.vbproj
rename to dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/vb/ColumnDefinitionsGrid.vbproj
index 6aa710cbc9..c6947d7ad4 100644
--- a/dotnet-desktop-guide/samples/snippets/visualbasic/VS_Snippets_Wpf/ColumnDefinitionsGrid/VisualBasic/ColumnDefinitionsGrid.vbproj
+++ b/dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/vb/ColumnDefinitionsGrid.vbproj
@@ -1,14 +1,19 @@
-<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003" ToolsVersion="4.0">
+<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003" ToolsVersion="12.0">
   <PropertyGroup>
     <AssemblyName>SDKSample</AssemblyName>
     <TargetType>winexe</TargetType>
     <Configuration Condition="'$(Configuration)'==''">Debug</Configuration>
     <SchemaVersion>2.0</SchemaVersion>
     <OutputPath>bin\$(Configuration)\</OutputPath>
-    <TargetFrameworkVersion>v4.0</TargetFrameworkVersion>
+    <TargetFrameworkVersion>v4.8</TargetFrameworkVersion>
     <ProjectTypeGuids>{60dc8134-eba5-43b8-bcc9-bb4bc16c2548};{F184B08F-C81C-45F6-A57F-5ABD9991F28F}</ProjectTypeGuids>
-    <TargetFrameworkProfile>Client</TargetFrameworkProfile>
+    <TargetFrameworkProfile>
+    </TargetFrameworkProfile>
     <ProductVersion>10.0.20821</ProductVersion>
+    <ProjectGuid>{9CD74B47-FC44-43A0-B18E-FFF7B4EA3EF8}</ProjectGuid>
+  </PropertyGroup>
+  <PropertyGroup Condition="'$(Configuration)|$(Platform)' == 'Debug|x86'">
+    <Prefer32Bit>false</Prefer32Bit>
   </PropertyGroup>
   <Import Project="$(MSBuildToolsPath)\Microsoft.VisualBasic.targets" />
   <ItemGroup>
@@ -39,4 +44,7 @@
       <SubType>Code</SubType>
     </Compile>
   </ItemGroup>
+  <ItemGroup>
+    <None Include="app.config" />
+  </ItemGroup>
 </Project>
\ No newline at end of file
diff --git a/dotnet-desktop-guide/samples/snippets/visualbasic/VS_Snippets_Wpf/ColumnDefinitionsGrid/VisualBasic/Window1.xaml b/dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/vb/Window1.xaml
similarity index 100%
rename from dotnet-desktop-guide/samples/snippets/visualbasic/VS_Snippets_Wpf/ColumnDefinitionsGrid/VisualBasic/Window1.xaml
rename to dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/vb/Window1.xaml
diff --git a/dotnet-desktop-guide/samples/snippets/visualbasic/VS_Snippets_Wpf/ColumnDefinitionsGrid/VisualBasic/Window1.xaml.vb b/dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/vb/Window1.xaml.vb
similarity index 100%
rename from dotnet-desktop-guide/samples/snippets/visualbasic/VS_Snippets_Wpf/ColumnDefinitionsGrid/VisualBasic/Window1.xaml.vb
rename to dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/vb/Window1.xaml.vb
diff --git a/dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/vb/app.config b/dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/vb/app.config
new file mode 100644
index 0000000000..b5cb6d50fc
--- /dev/null
+++ b/dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/vb/app.config
@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="utf-8"?>
+<configuration>
+    <system.diagnostics>
+        <sources>
+            <!-- This section defines the logging configuration for My.Application.Log -->
+            <source name="DefaultSource" switchName="DefaultSwitch">
+                <listeners>
+                    <add name="FileLog"/>
+                    <!-- Uncomment the below section to write to the Application Event Log -->
+                    <!--<add name="EventLog"/>-->
+                </listeners>
+            </source>
+        </sources>
+        <switches>
+            <add name="DefaultSwitch" value="Information"/>
+        </switches>
+        <sharedListeners>
+            <add name="FileLog" type="Microsoft.VisualBasic.Logging.FileLogTraceListener, Microsoft.VisualBasic, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL" initializeData="FileLogWriter"/>
+            <!-- Uncomment the below section and replace APPLICATION_NAME with the name of your application to write to the Application Event Log -->
+            <!--<add name="EventLog" type="System.Diagnostics.EventLogTraceListener" initializeData="APPLICATION_NAME"/> -->
+        </sharedListeners>
+    </system.diagnostics>
+<startup><supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.8"/></startup></configuration>
diff --git a/dotnet-desktop-guide/samples/snippets/visualbasic/VS_Snippets_Wpf/ColumnDefinitionsGrid/VisualBasic/app.xaml b/dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/vb/app.xaml
similarity index 100%
rename from dotnet-desktop-guide/samples/snippets/visualbasic/VS_Snippets_Wpf/ColumnDefinitionsGrid/VisualBasic/app.xaml
rename to dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/vb/app.xaml
diff --git a/dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/vb/snippets.5000.json b/dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/vb/snippets.5000.json
new file mode 100644
index 0000000000..9493e73361
--- /dev/null
+++ b/dotnet-desktop-guide/framework/wpf/controls/snippets/manipulate-columns-and-rows-by-using-columndefinitionscollections/vb/snippets.5000.json
@@ -0,0 +1,3 @@
+{
+    "host": "visualstudio"
+}
\ No newline at end of file
diff --git a/dotnet-desktop-guide/samples/snippets/csharp/VS_Snippets_Wpf/ColumnDefinitionsGrid/CSharp/Window1.xaml b/dotnet-desktop-guide/samples/snippets/csharp/VS_Snippets_Wpf/ColumnDefinitionsGrid/CSharp/Window1.xaml
deleted file mode 100644
index 2a15d60cfb..0000000000
--- a/dotnet-desktop-guide/samples/snippets/csharp/VS_Snippets_Wpf/ColumnDefinitionsGrid/CSharp/Window1.xaml
+++ /dev/null
@@ -1,54 +0,0 @@
-<Window  
-    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
-    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
-    x:Class="columndefinitions_grid.Window1"
-    Title="ColumnDefinitions Sample">
-    <Border BorderBrush="Black" Background="White" BorderThickness="2">
-	<DockPanel Margin="10,0,0,0">
-	
-		<TextBlock FontSize="20" FontWeight="Bold" DockPanel.Dock="Top">Grid Column and Row Collections</TextBlock>
-		<TextBlock DockPanel.Dock="Top">Click any of the buttons below to invoke the associated methods and properties of ColumnDefinition and RowDefinition Collections.</TextBlock>
-		<!-- <Snippet1> -->
-        <Grid DockPanel.Dock="Top" HorizontalAlignment="Left" Name="grid1" ShowGridLines="true" Width="625" Height="400" Background="#b0e0e6">
-          <Grid.ColumnDefinitions>
-            <ColumnDefinition/>
-            <ColumnDefinition/>
-            <ColumnDefinition/>
-          </Grid.ColumnDefinitions>
-          <Grid.RowDefinitions>
-          <RowDefinition/>
-            <RowDefinition/>
-            <RowDefinition/>
-          </Grid.RowDefinitions>
-        </Grid>
-
-        <StackPanel HorizontalAlignment="Left" Orientation="Horizontal" Width="625" DockPanel.Dock="Top">
-            <Button Width="125" Click="addCol">Add Column</Button>
-            <Button Width="125" Click="addRow">Add Row</Button>
-            <Button Width="125" Click="clearCol">Clear All Columns</Button>
-            <Button Width="125" Click="clearRow">Clear All Rows</Button>
-            <Button Width="125" Click="removeCol">Remove One Column</Button>
-        </StackPanel>
-        <StackPanel HorizontalAlignment="Left" Orientation="Horizontal" Width="625" DockPanel.Dock="Top">
-            <Button Width="125" Click="removeRow">Remove One Row</Button>
-            <Button Width="125" Click="colCount">How Many Columns?</Button>
-            <Button Width="125" Click="rowCount">How Many Rows?</Button>
-            <Button Width="125" Click="rem5Col">Remove 5 Columns</Button>
-            <Button Width="125" Click="rem5Row">Remove 5 Rows</Button>			
-		    </StackPanel>
-        <StackPanel HorizontalAlignment="Left" Orientation="Horizontal" Width="625" DockPanel.Dock="Top">
-            <Button Width="125" Click="containsRow">Contains Row?</Button>
-            <Button Width="125" Click="containsCol">Contains Column?</Button>
-            <Button Width="125" Click="insertRowAt">Insert Row</Button>
-            <Button Width="125" Click="insertColAt">Insert Column</Button>
-            <Button Width="125" Click="colReadOnly">IsReadOnly?</Button>
-        </StackPanel>    
-		<!-- </Snippet1> -->
-		<TextBlock DockPanel.Dock="Top" Name="tp1"/>
-        <TextBlock DockPanel.Dock="Top" Name="tp2"/>
-        <TextBlock DockPanel.Dock="Top" Name="tp3"/>
-        <TextBlock DockPanel.Dock="Top" Name="tp4"/>		
-        <TextBlock DockPanel.Dock="Top" Name="tp5"/>
-	</DockPanel>
-	</Border>	
-</Window>