From a8690ed3d867cbd85495e06e7795e947d920de82 Mon Sep 17 00:00:00 2001 From: Dennis Lee Date: Wed, 20 Feb 2019 17:23:24 -0800 Subject: [PATCH 1/5] Another 20 files with MSDN link fixes. --- ...designerserializationvisibilityattribute.md | 14 +++++++------- ...net-data-with-wf-bindingsource-component.md | 2 +- ...container-control-overview-windows-forms.md | 2 +- .../splitcontainer-control-windows-forms.md | 2 +- .../controls/statusstrip-control-overview.md | 2 +- .../winforms/controls/statusstrip-control.md | 2 +- .../tablelayoutpanel-control-overview.md | 2 +- .../tablelayoutpanel-control-windows-forms.md | 4 ++-- .../timer-component-overview-windows-forms.md | 2 +- .../controls/timer-component-windows-forms.md | 2 +- .../toolstrip-control-windows-forms.md | 6 +++--- .../controls/toolstrip-technology-summary.md | 18 +++++++++--------- .../controls/toolstripcontainer-control.md | 2 +- .../toolstrippanel-control-overview.md | 2 +- ...shooting-control-and-component-authoring.md | 7 +++---- ...ound-column-to-a-data-bound-datagridview.md | 2 +- ...g-the-managed-html-document-object-model.md | 3 --- .../controls/varieties-of-custom-controls.md | 8 ++++---- ...ontrols-on-windows-forms-using-snaplines.md | 2 +- ...-professionally-styled-toolstrip-control.md | 6 +++--- 20 files changed, 43 insertions(+), 47 deletions(-) diff --git a/docs/framework/winforms/controls/serializing-collections-designerserializationvisibilityattribute.md b/docs/framework/winforms/controls/serializing-collections-designerserializationvisibilityattribute.md index 97cf7d8dc9edc..87d9a2b050c08 100644 --- a/docs/framework/winforms/controls/serializing-collections-designerserializationvisibilityattribute.md +++ b/docs/framework/winforms/controls/serializing-collections-designerserializationvisibilityattribute.md @@ -15,7 +15,7 @@ ms.assetid: 020c9df4-fdc5-4dae-815a-963ecae5668c # Walkthrough: Serializing Collections of Standard Types with the DesignerSerializationVisibilityAttribute Your custom controls will sometimes expose a collection as a property. This walkthrough demonstrates how to use the class to control how a collection is serialized at design time. Applying the value to your collection property ensures that the property will be serialized. - To copy the code in this topic as a single listing, see [How to: Serialize Collections of Standard Types with the DesignerSerializationVisibilityAttribute](https://msdn.microsoft.com/library/7829fcdd-8205-405f-8231-a1282a9835c9). + To copy the code in this topic as a single listing, see [How to: Serialize Collections of Standard Types with the DesignerSerializationVisibilityAttribute](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2013/ms171833(v=vs.120)). > [!NOTE] > The dialog boxes and menu commands you see might differ from those described in Help depending on your active settings or edition. To change your settings, choose **Import and Export Settings** on the **Tools** menu. For more information, see [Personalize the Visual Studio IDE](/visualstudio/ide/personalizing-the-visual-studio-ide). @@ -30,9 +30,9 @@ Your custom controls will sometimes expose a collection as a property. This walk #### To create a control with a serializable collection -1. Create a Windows Control Library project called `SerializationDemoControlLib`. For more information, see [Windows Control Library Template](https://msdn.microsoft.com/library/722f4e2d-1310-4ed5-8f33-593337ab66b4). +1. Create a Windows Control Library project called `SerializationDemoControlLib`. For more information, see [Windows Control Library Template](https://docs.microsoft.com/previous-versions/kxczf775(v=vs.100)). -2. Rename `UserControl1` to `SerializationDemoControl`. For more information, see [How to: Rename Identifiers](https://msdn.microsoft.com/library/2430f732-2b70-4516-8cf6-a7bb71cc9724). +2. Rename `UserControl1` to `SerializationDemoControl`. For more information, see [Rename a code symbol refactoring](/visualstudio/ide/reference/rename). 3. In the **Properties** window, set the value of the property to `10`. @@ -123,16 +123,16 @@ Your custom controls will sometimes expose a collection as a property. This walk ## Next Steps Once you know how to serialize a collection of standard types, consider integrating your custom controls more deeply into the design-time environment. The following topics describe how to enhance the design-time integration of your custom controls: -- [Design-Time Architecture](https://msdn.microsoft.com/library/4881917b-628f-4689-b872-472e4f8a4e3a) +- [Design-Time Architecture](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2013/c5z9s1h4(v=vs.120)) - [Attributes in Windows Forms Controls](../../../../docs/framework/winforms/controls/attributes-in-windows-forms-controls.md) -- [Designer Serialization Overview](https://msdn.microsoft.com/library/c342635a-aa5f-4281-915b-b013738af15a) +- [Designer Serialization Overview](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2013/ms171834(v=vs.120)) - [Walkthrough: Creating a Windows Forms Control That Takes Advantage of Visual Studio Design-Time Features](../../../../docs/framework/winforms/controls/creating-a-wf-control-design-time-features.md) ## See also - -- [Designer Serialization Overview](https://msdn.microsoft.com/library/c342635a-aa5f-4281-915b-b013738af15a) -- [How to: Serialize Collections of Standard Types with the DesignerSerializationVisibilityAttribute](https://msdn.microsoft.com/library/7829fcdd-8205-405f-8231-a1282a9835c9) +- [Designer Serialization Overview](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2013/ms171834(v=vs.120)) +- [How to: Serialize Collections of Standard Types with the DesignerSerializationVisibilityAttribute](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2013/ms171833(v=vs.120)) - [Walkthrough: Automatically Populating the Toolbox with Custom Components](../../../../docs/framework/winforms/controls/walkthrough-automatically-populating-the-toolbox-with-custom-components.md) diff --git a/docs/framework/winforms/controls/sort-and-filter-ado-net-data-with-wf-bindingsource-component.md b/docs/framework/winforms/controls/sort-and-filter-ado-net-data-with-wf-bindingsource-component.md index 77bb7a0466729..53add6872ae65 100644 --- a/docs/framework/winforms/controls/sort-and-filter-ado-net-data-with-wf-bindingsource-component.md +++ b/docs/framework/winforms/controls/sort-and-filter-ado-net-data-with-wf-bindingsource-component.md @@ -50,5 +50,5 @@ You can expose the sorting and filtering capability of - -- [How to: Install Sample Databases](https://msdn.microsoft.com/library/ed1291f6-604c-4972-ae22-0345c6dea12e) +- [How to: Install Sample Databases](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2013/8b6y4c7s(v=vs.120)) - [BindingSource Component](../../../../docs/framework/winforms/controls/bindingsource-component.md) diff --git a/docs/framework/winforms/controls/splitcontainer-control-overview-windows-forms.md b/docs/framework/winforms/controls/splitcontainer-control-overview-windows-forms.md index 492116af701f4..eeba393c85ab9 100644 --- a/docs/framework/winforms/controls/splitcontainer-control-overview-windows-forms.md +++ b/docs/framework/winforms/controls/splitcontainer-control-overview-windows-forms.md @@ -46,4 +46,4 @@ The Windows Forms control can be thou ## See also - - [SplitContainer Control](../../../../docs/framework/winforms/controls/splitcontainer-control-windows-forms.md) -- [SplitContainer Control Sample](https://msdn.microsoft.com/library/9015fad0-7108-4d85-a83a-a72d038c4f65) +- [SplitContainer Control Sample](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2008/0ffz7d1b(v=vs.90)) diff --git a/docs/framework/winforms/controls/splitcontainer-control-windows-forms.md b/docs/framework/winforms/controls/splitcontainer-control-windows-forms.md index b7a70cac8a7d2..8a8689811253a 100644 --- a/docs/framework/winforms/controls/splitcontainer-control-windows-forms.md +++ b/docs/framework/winforms/controls/splitcontainer-control-windows-forms.md @@ -27,7 +27,7 @@ The Windows Forms `SplitContainer` control can be thought of as a composite; it [How to: Create a Multipane User Interface with Windows Forms](../../../../docs/framework/winforms/controls/how-to-create-a-multipane-user-interface-with-windows-forms.md) Creates a multi-pane user interface that is similar to the one used in Microsoft Outlook. - Also see [How to: Split a Window Horizontally Using the Designer](how-to-split-a-window-horizontally-using-the-designer.md), [How to: Create a Windows Explorer–Style Interface on a Windows Form](https://msdn.microsoft.com/library/zh2fe5a5\(v=vs.110\)), [How to: Create a Multipane User Interface with Windows Forms Using the Designer](create-a-multipane-user-interface-with-wf-using-the-designer.md). + Also see [How to: Split a Window Horizontally Using the Designer](how-to-split-a-window-horizontally-using-the-designer.md), [How to: Create a Windows Explorer–Style Interface on a Windows Form](how-to-create-a-windows-explorer-style-interface-on-a-windows-form.md), [How to: Create a Multipane User Interface with Windows Forms Using the Designer](create-a-multipane-user-interface-with-wf-using-the-designer.md). ## Reference class diff --git a/docs/framework/winforms/controls/statusstrip-control-overview.md b/docs/framework/winforms/controls/statusstrip-control-overview.md index 14f2db687b415..1dc5421ea0e18 100644 --- a/docs/framework/winforms/controls/statusstrip-control-overview.md +++ b/docs/framework/winforms/controls/statusstrip-control-overview.md @@ -15,7 +15,7 @@ A control displays information about an There is extensive support for handling items and common commands in Visual Studio. - Also see [StatusStrip Items Collection Editor](https://msdn.microsoft.com/library/ms233631\(v=vs.110\)), [StatusStrip Tasks Dialog Box](https://msdn.microsoft.com/library/ms233642\(v=vs.110\)). + Also see [StatusStrip Items Collection Editor](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233631(v=vs.100)) and [StatusStrip Tasks Dialog Box](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233642(v=vs.100)). Although replaces and extends the control of previous versions, is retained for both backward compatibility and future use if you choose. diff --git a/docs/framework/winforms/controls/statusstrip-control.md b/docs/framework/winforms/controls/statusstrip-control.md index a98b6305cb661..7e4601165ccd1 100644 --- a/docs/framework/winforms/controls/statusstrip-control.md +++ b/docs/framework/winforms/controls/statusstrip-control.md @@ -16,7 +16,7 @@ The Windows Forms `StatusStrip` control is used on forms as an area, usually dis [How to: Use the Spring Property Interactively in a StatusStrip](../../../../docs/framework/winforms/controls/how-to-use-the-spring-property-interactively-in-a-statusstrip.md) Demonstrates using the `Spring` property to interactively center a `ToolStripStatusLabel` in a `StatusStrip`. - Also see [StatusStrip Items Collection Editor](https://msdn.microsoft.com/library/ms233631\(v=vs.110\)), [StatusStrip Items Collection Editor](https://msdn.microsoft.com/library/ms233642\(v=vs.110\)). + Also see [StatusStrip Items Collection Editor](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233631(v=vs.100)) and [StatusStrip Tasks Dialog Box](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233642(v=vs.100)). ## Reference diff --git a/docs/framework/winforms/controls/tablelayoutpanel-control-overview.md b/docs/framework/winforms/controls/tablelayoutpanel-control-overview.md index a649f6941078e..d2f017d1e9e7b 100644 --- a/docs/framework/winforms/controls/tablelayoutpanel-control-overview.md +++ b/docs/framework/winforms/controls/tablelayoutpanel-control-overview.md @@ -33,7 +33,7 @@ The control arranges its contents i 3. [How to: Edit Columns and Rows in a TableLayoutPanel Control](how-to-edit-columns-and-rows-in-a-tablelayoutpanel-control.md) -4. [Walkthrough: Arranging Controls on Windows Forms Using a TableLayoutPanel](https://msdn.microsoft.com/library/w4yc3e8c\(v=vs.110\)) +4. [Walkthrough: Arranging Controls on Windows Forms Using a TableLayoutPanel](walkthrough-arranging-controls-on-windows-forms-using-a-tablelayoutpanel.md) ## See also - diff --git a/docs/framework/winforms/controls/tablelayoutpanel-control-windows-forms.md b/docs/framework/winforms/controls/tablelayoutpanel-control-windows-forms.md index 9ee2fed41b1c1..89aa6abc51e43 100644 --- a/docs/framework/winforms/controls/tablelayoutpanel-control-windows-forms.md +++ b/docs/framework/winforms/controls/tablelayoutpanel-control-windows-forms.md @@ -38,7 +38,7 @@ The control arranges its contents i 3. [How to: Edit Columns and Rows in a TableLayoutPanel Control](how-to-edit-columns-and-rows-in-a-tablelayoutpanel-control.md) -4. [Walkthrough: Arranging Controls on Windows Forms Using a TableLayoutPanel](https://msdn.microsoft.com/library/w4yc3e8c\(v=vs.110\)) +4. [Walkthrough: Arranging Controls on Windows Forms Using a TableLayoutPanel](walkthrough-arranging-controls-on-windows-forms-using-a-tablelayoutpanel.md) ## Reference @@ -54,4 +54,4 @@ The control arranges its contents i [Localization](../../../../docs/standard/globalization-localization/localization.md) Provides an overview of topics relating to localization. - Also see [Localizing Applications](https://msdn.microsoft.com/library/z68135h5\(v=vs.110\)) or [Localizing Applications](https://msdn.microsoft.com/library/z68135h5\(v=vs.120\)) + Also see [Localizing Applications](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2013/z68135h5(v=vs.120)). diff --git a/docs/framework/winforms/controls/timer-component-overview-windows-forms.md b/docs/framework/winforms/controls/timer-component-overview-windows-forms.md index d7be17a92e1bc..607d00fad0dda 100644 --- a/docs/framework/winforms/controls/timer-component-overview-windows-forms.md +++ b/docs/framework/winforms/controls/timer-component-overview-windows-forms.md @@ -9,7 +9,7 @@ helpviewer_keywords: ms.assetid: e672c05b-a8b6-4b26-9e4d-9223aa9e3873 --- # Timer Component Overview (Windows Forms) -The Windows Forms is a component that raises an event at regular intervals. This component is designed for a Windows Forms environment. If you need a timer that is suitable for a server environment, see [Introduction to Server-Based Timers](https://msdn.microsoft.com/library/adc0bc0a-a519-4812-bafc-fb9d1a5801fc). +The Windows Forms is a component that raises an event at regular intervals. This component is designed for a Windows Forms environment. If you need a timer that is suitable for a server environment, see [Introduction to Server-Based Timers](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2008/tb9yt5e6(v=vs.90)). ## Key Properties, Methods, and Events The length of the intervals is defined by the property, whose value is in milliseconds. When the component is enabled, the event is raised every interval. This is where you would add code to be executed. For more information, see [How to: Run Procedures at Set Intervals with the Windows Forms Timer Component](../../../../docs/framework/winforms/controls/run-procedures-at-set-intervals-with-wf-timer-component.md). The key methods of the component are and , which turn the timer on and off. When the timer is switched off, it resets; there is no way to pause a component. diff --git a/docs/framework/winforms/controls/timer-component-windows-forms.md b/docs/framework/winforms/controls/timer-component-windows-forms.md index 3bac9e0266bcc..4718707335c1d 100644 --- a/docs/framework/winforms/controls/timer-component-windows-forms.md +++ b/docs/framework/winforms/controls/timer-component-windows-forms.md @@ -31,5 +31,5 @@ The Windows Forms is a component that raises a [Controls to Use on Windows Forms](../../../../docs/framework/winforms/controls/controls-to-use-on-windows-forms.md) Provides a complete list of Windows Forms controls, with links to information on their use. - [Timer Control for Visual Basic 6.0 Users](https://msdn.microsoft.com/library/38e5184a-1e50-45cf-b936-dae566c0cfc5) + [Timer Control for Visual Basic 6.0 Users](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2008/zffx82xt(v=vs.90)) Describes how timer functionality has changed in Visual Basic as compared to previous versions. diff --git a/docs/framework/winforms/controls/toolstrip-control-windows-forms.md b/docs/framework/winforms/controls/toolstrip-control-windows-forms.md index c755bce877213..d90b4e0af0897 100644 --- a/docs/framework/winforms/controls/toolstrip-control-windows-forms.md +++ b/docs/framework/winforms/controls/toolstrip-control-windows-forms.md @@ -67,7 +67,7 @@ ms.assetid: e5ef455a-e049-429c-8005-30c93132fb79 [How to: Implement a Custom ToolStripRenderer](../../../../docs/framework/winforms/controls/how-to-implement-a-custom-toolstriprenderer.md) Describes how to customize the appearance of a control by implementing a class that derives from . -- [How to: Create a Basic Windows Forms ToolStrip with Standard Items Using the Designer](https://msdn.microsoft.com/library/571c1z99\(v=vs.110\)) +- [How to: Create a Basic Windows Forms ToolStrip with Standard Items Using the Designer](create-a-basic-wf-toolstrip-with-standard-items-using-the-designer.md) - [How to: Move a ToolStrip Out of a ToolStripContainer onto a Form](how-to-move-a-toolstrip-out-of-a-toolstripcontainer-onto-a-form.md) @@ -75,9 +75,9 @@ ms.assetid: e5ef455a-e049-429c-8005-30c93132fb79 - [Walkthrough: Creating an MDI Form with Menu Merging and ToolStrip Controls](walkthrough-creating-an-mdi-form-with-menu-merging-and-toolstrip-controls.md) -- [ToolStrip Tasks Dialog Box](https://msdn.microsoft.com/library/ms233648\(v=vs.110\)) +- [ToolStrip Tasks Dialog Box](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233648(v=vs.100)) -- [ToolStrip Items Collection Editor](https://msdn.microsoft.com/library/ms233643\(v=vs.110\)) +- [ToolStrip Items Collection Editor](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233643(v=vs.100)) ## Reference class diff --git a/docs/framework/winforms/controls/toolstrip-technology-summary.md b/docs/framework/winforms/controls/toolstrip-technology-summary.md index 1578e73ab7fb4..af276b8d1606f 100644 --- a/docs/framework/winforms/controls/toolstrip-technology-summary.md +++ b/docs/framework/winforms/controls/toolstrip-technology-summary.md @@ -57,26 +57,26 @@ This topic summarizes information about the `ToolStrip` control and the classes ### Task Dialog Boxes In Visual Studio, clicking the smart tag on a control in the designer displays a task list for convenient access to many frequently used commands. -- [MenuStrip Tasks Dialog Box](https://msdn.microsoft.com/library/ms233645\(v=vs.110\)) +- [MenuStrip Tasks Dialog Box](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233645(v=vs.100)) -- [ToolStrip Tasks Dialog Box](https://msdn.microsoft.com/library/ms233648\(v=vs.110\)) +- [ToolStrip Tasks Dialog Box](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233648(v=vs.100)) -- [ContextMenuStrip Tasks Dialog Box](https://msdn.microsoft.com/library/ms233646\(v=vs.110\)) +- [ContextMenuStrip Tasks Dialog Box](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233646(v=vs.100)) -- [StatusStrip Tasks Dialog Box](https://msdn.microsoft.com/library/ms233642\(v=vs.110\)) +- [StatusStrip Tasks Dialog Box](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233642(v=vs.100)) -- [ToolStripContainer Tasks Dialog Box](https://msdn.microsoft.com/library/ms233647\(v=vs.110\)) +- [ToolStripContainer Tasks Dialog Box](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233647(v=vs.100)) ### Items Collection Editors In Visual Studio, when you click **Edit Items** on the task list or right-click the control and select **Edit Items** in the shortcut menu, the collection editor for the control is displayed. Collection editors let you add, remove, and reorder items that the control contains. You can also view and change the properties for the control and the control's items. -- [MenuStrip Items Collection Editor](https://msdn.microsoft.com/library/ms233625\(v=vs.110\)) +- [MenuStrip Items Collection Editor](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233625(v=vs.100)) -- [StatusStrip Items Collection Editor](https://msdn.microsoft.com/library/ms233631\(v=vs.110\)) +- [StatusStrip Items Collection Editor](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233631(v=vs.100)) -- [ContextMenuStrip Items Collection Editor](https://msdn.microsoft.com/library/ms233641\(v=vs.110\)) +- [ContextMenuStrip Items Collection Editor](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233641(v=vs.100)) -- [ToolStrip Items Collection Editor](https://msdn.microsoft.com/library/ms233643\(v=vs.110\)) +- [ToolStrip Items Collection Editor](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233643(v=vs.100)) ## Hosting Controls The class provides built-in wrappers for , , and controls. You can also host any other existing or COM control in a . diff --git a/docs/framework/winforms/controls/toolstripcontainer-control.md b/docs/framework/winforms/controls/toolstripcontainer-control.md index 3c8c9d08c5e15..742699a334660 100644 --- a/docs/framework/winforms/controls/toolstripcontainer-control.md +++ b/docs/framework/winforms/controls/toolstripcontainer-control.md @@ -29,7 +29,7 @@ ms.assetid: 378fa5b4-38e1-46f4-8e5c-d0c19dcd0200 Provides reference documentation for the of a control. - Also see [ToolStripContainer Tasks Dialog Box](https://msdn.microsoft.com/library/ms233647\(v=vs.110\)). + Also see [ToolStripContainer Tasks Dialog Box](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233647(v=vs.100)). ## Related Sections diff --git a/docs/framework/winforms/controls/toolstrippanel-control-overview.md b/docs/framework/winforms/controls/toolstrippanel-control-overview.md index a01d7b7b16567..539ea6c17e9d2 100644 --- a/docs/framework/winforms/controls/toolstrippanel-control-overview.md +++ b/docs/framework/winforms/controls/toolstrippanel-control-overview.md @@ -25,4 +25,4 @@ A provides a single area for position ## See also - - -- [ToolStrip Sample](https://msdn.microsoft.com/library/b7352439-184a-4a3a-b2ad-07465d3af9ed) +- [ToolStrip Sample](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2008/ms181005(v=vs.90)) diff --git a/docs/framework/winforms/controls/troubleshooting-control-and-component-authoring.md b/docs/framework/winforms/controls/troubleshooting-control-and-component-authoring.md index 850e000fbcde2..501321a3fadc1 100644 --- a/docs/framework/winforms/controls/troubleshooting-control-and-component-authoring.md +++ b/docs/framework/winforms/controls/troubleshooting-control-and-component-authoring.md @@ -13,7 +13,7 @@ helpviewer_keywords: ms.assetid: e9c8c099-2271-4737-882f-50f336c7a55e --- # Troubleshooting Control and Component Authoring -This topic lists the following common problems that arise when developing components and controls. For more information, see [Programming with Components](https://msdn.microsoft.com/library/d4d4fcb4-e0b8-46b3-b679-7ee0026eb9e3). +This topic lists the following common problems that arise when developing components and controls. - Cannot Add Control to Toolbox @@ -106,6 +106,5 @@ This topic lists the following common problems that arise when developing compon - [Walkthrough: Automatically Populating the Toolbox with Custom Components](../../../../docs/framework/winforms/controls/walkthrough-automatically-populating-the-toolbox-with-custom-components.md) - [How to: Test the Run-Time Behavior of a UserControl](../../../../docs/framework/winforms/controls/how-to-test-the-run-time-behavior-of-a-usercontrol.md) - [Walkthrough: Debugging Custom Windows Forms Controls at Design Time](../../../../docs/framework/winforms/controls/walkthrough-debugging-custom-windows-forms-controls-at-design-time.md) -- [Component Authoring](https://msdn.microsoft.com/library/4a5a5e49-0378-4a31-83bc-24da0f1a727d) -- [Troubleshooting Design-Time Development](https://msdn.microsoft.com/library/e048d08e-fa7c-4be8-b238-4abaa199a0a6) -- [Programming with Components](https://msdn.microsoft.com/library/d4d4fcb4-e0b8-46b3-b679-7ee0026eb9e3) +- [Component Authoring](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2013/5dya64wy(v=vs.120)) +- [Troubleshooting Design-Time Development](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2013/ms171843(v=vs.120)) diff --git a/docs/framework/winforms/controls/unbound-column-to-a-data-bound-datagridview.md b/docs/framework/winforms/controls/unbound-column-to-a-data-bound-datagridview.md index c46a002163283..30e9d7ffa8a1b 100644 --- a/docs/framework/winforms/controls/unbound-column-to-a-data-bound-datagridview.md +++ b/docs/framework/winforms/controls/unbound-column-to-a-data-bound-datagridview.md @@ -15,7 +15,7 @@ The data you display in the control wil The following code example demonstrates how to create an unbound column of **Details** buttons to display a child table related to a particular row in a parent table when you implement a master/detail scenario. To respond to button clicks, implement a event handler that displays a form containing the child table. - There is support for this task in Visual Studio. Also see [How to: Add and Remove Columns in the Windows Forms DataGridView Control Using the Designer](https://msdn.microsoft.com/library/dyyesckz\(v=vs.110\)) + There is support for this task in Visual Studio. Also see [How to: Add and Remove Columns in the Windows Forms DataGridView Control Using the Designer](add-and-remove-columns-in-the-datagrid-using-the-designer.md). ## Example [!code-csharp[System.Windows.Forms.DataGridViewMisc#010](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.DataGridViewMisc/CS/datagridviewmisc.cs#010)] diff --git a/docs/framework/winforms/controls/using-the-managed-html-document-object-model.md b/docs/framework/winforms/controls/using-the-managed-html-document-object-model.md index 1eb5db4a22544..115b72693bdf6 100644 --- a/docs/framework/winforms/controls/using-the-managed-html-document-object-model.md +++ b/docs/framework/winforms/controls/using-the-managed-html-document-object-model.md @@ -33,6 +33,3 @@ The managed HTML document object model (DOM) provides a wrapper based on the [!I ## Related Sections [WebBrowser Control](../../../../docs/framework/winforms/controls/webbrowser-control-windows-forms.md) - -## See also -- [About the DHTML Object Model](https://msdn.microsoft.com/library/default.asp?url=/workshop/author/om/doc_object.asp) diff --git a/docs/framework/winforms/controls/varieties-of-custom-controls.md b/docs/framework/winforms/controls/varieties-of-custom-controls.md index e74a27697a1f6..c33f73159f3f6 100644 --- a/docs/framework/winforms/controls/varieties-of-custom-controls.md +++ b/docs/framework/winforms/controls/varieties-of-custom-controls.md @@ -18,7 +18,7 @@ With the .NET Framework, you can develop and implement new controls. You can ext Deciding which kind of control to create can be confusing. This topic highlights the differences among the various kinds of controls from which you can inherit, and provides you with information about how to choose a particular kind of control for your project. > [!NOTE] -> For information about authoring a control to use on Web Forms, see [Developing Custom ASP.NET Server Controls](https://msdn.microsoft.com/library/fbe26c16-cff4-4089-b3dd-877411f0c0ef). +> For information about authoring a control to use on Web Forms, see [Developing Custom ASP.NET Server Controls](https://docs.microsoft.com/previous-versions/aspnet/zt27tfhy(v=vs.100)). ## Base Control Class The class is the base class for Windows Forms controls. It provides the infrastructure required for visual display in Windows Forms applications. @@ -98,11 +98,11 @@ With the .NET Framework, you can develop and implement new controls. You can ext ## Custom Design Experience If you need to implement a custom design-time experience, you can author your own designer. For composite controls, derive your custom designer class from the or the classes. For extended and custom controls, derive your custom designer class from the class. - Use the to associate your control with your designer. For more information, see [Extending Design-Time Support](https://msdn.microsoft.com/library/d6ac8a6a-42fd-4bc8-bf33-b212811297e2) and [How to: Create a Windows Forms Control That Takes Advantage of Design-Time Features](https://msdn.microsoft.com/library/8e0bad0e-56f3-43d2-bf63-a945c654d97c). + Use the to associate your control with your designer. For more information, see [Extending Design-Time Support](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2013/37899azc(v=vs.120)) and [How to: Create a Windows Forms Control That Takes Advantage of Design-Time Features](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2013/307hck25(v=vs.120)). ## See also - [Developing Custom Windows Forms Controls with the .NET Framework](../../../../docs/framework/winforms/controls/developing-custom-windows-forms-controls.md) - [How to: Develop a Simple Windows Forms Control](../../../../docs/framework/winforms/controls/how-to-develop-a-simple-windows-forms-control.md) - [Developing a Composite Windows Forms Control](../../../../docs/framework/winforms/controls/developing-a-composite-windows-forms-control.md) -- [Extending Design-Time Support](https://msdn.microsoft.com/library/d6ac8a6a-42fd-4bc8-bf33-b212811297e2) -- [How to: Create a Windows Forms Control That Takes Advantage of Design-Time Features](https://msdn.microsoft.com/library/8e0bad0e-56f3-43d2-bf63-a945c654d97c) +- [Extending Design-Time Support](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2013/37899azc(v=vs.120)) +- [How to: Create a Windows Forms Control That Takes Advantage of Design-Time Features](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2013/307hck25(v=vs.120)) diff --git a/docs/framework/winforms/controls/walkthrough-arranging-controls-on-windows-forms-using-snaplines.md b/docs/framework/winforms/controls/walkthrough-arranging-controls-on-windows-forms-using-snaplines.md index 2b4d4fb9c4574..b4f280766badd 100644 --- a/docs/framework/winforms/controls/walkthrough-arranging-controls-on-windows-forms-using-snaplines.md +++ b/docs/framework/winforms/controls/walkthrough-arranging-controls-on-windows-forms-using-snaplines.md @@ -216,7 +216,7 @@ Precise placement of controls on your form is a high priority for many applicati #### To disable snaplines in the design environment -1. From the **Tools** menu, open the **Options** dialog box. Open the Windows Forms Designer dialog box. For details, see [General, Windows Forms Designer, Options Dialog Box](https://msdn.microsoft.com/library/8dd170af-72f0-4212-b04b-034ceee92834). +1. From the **Tools** menu, open the **Options** dialog box. Open the Windows Forms Designer dialog box. For details, see [General, Windows Forms Designer, Options Dialog Box](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/5aazxs78(v=vs.100)). 2. Select the **General** node. In the **Layout Mode** section, change the selection from **SnapLines** to **SnapToGrid**. diff --git a/docs/framework/winforms/controls/walkthrough-creating-a-professionally-styled-toolstrip-control.md b/docs/framework/winforms/controls/walkthrough-creating-a-professionally-styled-toolstrip-control.md index beab23e448a4c..01014e560d7ea 100644 --- a/docs/framework/winforms/controls/walkthrough-creating-a-professionally-styled-toolstrip-control.md +++ b/docs/framework/winforms/controls/walkthrough-creating-a-professionally-styled-toolstrip-control.md @@ -43,7 +43,7 @@ You can give your application’s controls 2. In **Solution Explorer**, delete the project's default control by deleting the source file named "UserControl1.cs" or "UserControl1.vb", depending on your language of choice. - For more information, see [NIB:How to: Remove, Delete, and Exclude Items](https://msdn.microsoft.com/library/6dffdc86-29c8-4eff-bcd8-e3a0dd9e9a73). + For more information, see [How to: Remove, Delete, and Exclude Items](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/0ebzhwsk(v=vs.100)). 3. Add a new item to the **StackViewLibrary** project. Give the new source file a base name of `StackView`. @@ -115,7 +115,7 @@ You can give your application’s controls 8. Rename the `mailStackButton_Click` event handler to `stackButton_Click`. - For more information, see [How to: Rename an Identifier (Visual Basic)](https://msdn.microsoft.com/library/e5a5edf8-3dba-4119-81f4-fc2aba180e0c). + For more information, see [Rename a code symbol refactoring](/visualstudio/ide/reference/rename). 9. Insert the following code into the `stackButton_Click` event handler. @@ -129,7 +129,7 @@ You can give your application’s controls 12. Repeat steps 10 and 11 for the `contactsStackButton` and `tasksStackButton` controls. ## Defining Icons - Each `StackView` button has an associated icon. For convenience, each icon is represented as a Base64-encoded string, which is deserialized before a is created from it. In a production environment, you store bitmap data as a resource, and your icons appear in the Windows Forms Designer. For more information, see [How to: Add Background Images to Windows Forms](https://msdn.microsoft.com/library/7a509ba2-055c-4ae6-b88a-54625c6d9aff). + Each `StackView` button has an associated icon. For convenience, each icon is represented as a Base64-encoded string, which is deserialized before a is created from it. In a production environment, you store bitmap data as a resource, and your icons appear in the Windows Forms Designer. For more information, see [How to: Add Background Images to Windows Forms](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/dff9f95f(v=vs.100)). #### To define icons From a00c8630f00b752583fe62d5dac6a7d19b307d7f Mon Sep 17 00:00:00 2001 From: Dennis Lee Date: Wed, 20 Feb 2019 17:24:06 -0800 Subject: [PATCH 2/5] Revert "Another 20 files with MSDN link fixes." This reverts commit a8690ed3d867cbd85495e06e7795e947d920de82. --- ...designerserializationvisibilityattribute.md | 14 +++++++------- ...net-data-with-wf-bindingsource-component.md | 2 +- ...container-control-overview-windows-forms.md | 2 +- .../splitcontainer-control-windows-forms.md | 2 +- .../controls/statusstrip-control-overview.md | 2 +- .../winforms/controls/statusstrip-control.md | 2 +- .../tablelayoutpanel-control-overview.md | 2 +- .../tablelayoutpanel-control-windows-forms.md | 4 ++-- .../timer-component-overview-windows-forms.md | 2 +- .../controls/timer-component-windows-forms.md | 2 +- .../toolstrip-control-windows-forms.md | 6 +++--- .../controls/toolstrip-technology-summary.md | 18 +++++++++--------- .../controls/toolstripcontainer-control.md | 2 +- .../toolstrippanel-control-overview.md | 2 +- ...shooting-control-and-component-authoring.md | 7 ++++--- ...ound-column-to-a-data-bound-datagridview.md | 2 +- ...g-the-managed-html-document-object-model.md | 3 +++ .../controls/varieties-of-custom-controls.md | 8 ++++---- ...ontrols-on-windows-forms-using-snaplines.md | 2 +- ...-professionally-styled-toolstrip-control.md | 6 +++--- 20 files changed, 47 insertions(+), 43 deletions(-) diff --git a/docs/framework/winforms/controls/serializing-collections-designerserializationvisibilityattribute.md b/docs/framework/winforms/controls/serializing-collections-designerserializationvisibilityattribute.md index 87d9a2b050c08..97cf7d8dc9edc 100644 --- a/docs/framework/winforms/controls/serializing-collections-designerserializationvisibilityattribute.md +++ b/docs/framework/winforms/controls/serializing-collections-designerserializationvisibilityattribute.md @@ -15,7 +15,7 @@ ms.assetid: 020c9df4-fdc5-4dae-815a-963ecae5668c # Walkthrough: Serializing Collections of Standard Types with the DesignerSerializationVisibilityAttribute Your custom controls will sometimes expose a collection as a property. This walkthrough demonstrates how to use the class to control how a collection is serialized at design time. Applying the value to your collection property ensures that the property will be serialized. - To copy the code in this topic as a single listing, see [How to: Serialize Collections of Standard Types with the DesignerSerializationVisibilityAttribute](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2013/ms171833(v=vs.120)). + To copy the code in this topic as a single listing, see [How to: Serialize Collections of Standard Types with the DesignerSerializationVisibilityAttribute](https://msdn.microsoft.com/library/7829fcdd-8205-405f-8231-a1282a9835c9). > [!NOTE] > The dialog boxes and menu commands you see might differ from those described in Help depending on your active settings or edition. To change your settings, choose **Import and Export Settings** on the **Tools** menu. For more information, see [Personalize the Visual Studio IDE](/visualstudio/ide/personalizing-the-visual-studio-ide). @@ -30,9 +30,9 @@ Your custom controls will sometimes expose a collection as a property. This walk #### To create a control with a serializable collection -1. Create a Windows Control Library project called `SerializationDemoControlLib`. For more information, see [Windows Control Library Template](https://docs.microsoft.com/previous-versions/kxczf775(v=vs.100)). +1. Create a Windows Control Library project called `SerializationDemoControlLib`. For more information, see [Windows Control Library Template](https://msdn.microsoft.com/library/722f4e2d-1310-4ed5-8f33-593337ab66b4). -2. Rename `UserControl1` to `SerializationDemoControl`. For more information, see [Rename a code symbol refactoring](/visualstudio/ide/reference/rename). +2. Rename `UserControl1` to `SerializationDemoControl`. For more information, see [How to: Rename Identifiers](https://msdn.microsoft.com/library/2430f732-2b70-4516-8cf6-a7bb71cc9724). 3. In the **Properties** window, set the value of the property to `10`. @@ -123,16 +123,16 @@ Your custom controls will sometimes expose a collection as a property. This walk ## Next Steps Once you know how to serialize a collection of standard types, consider integrating your custom controls more deeply into the design-time environment. The following topics describe how to enhance the design-time integration of your custom controls: -- [Design-Time Architecture](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2013/c5z9s1h4(v=vs.120)) +- [Design-Time Architecture](https://msdn.microsoft.com/library/4881917b-628f-4689-b872-472e4f8a4e3a) - [Attributes in Windows Forms Controls](../../../../docs/framework/winforms/controls/attributes-in-windows-forms-controls.md) -- [Designer Serialization Overview](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2013/ms171834(v=vs.120)) +- [Designer Serialization Overview](https://msdn.microsoft.com/library/c342635a-aa5f-4281-915b-b013738af15a) - [Walkthrough: Creating a Windows Forms Control That Takes Advantage of Visual Studio Design-Time Features](../../../../docs/framework/winforms/controls/creating-a-wf-control-design-time-features.md) ## See also - -- [Designer Serialization Overview](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2013/ms171834(v=vs.120)) -- [How to: Serialize Collections of Standard Types with the DesignerSerializationVisibilityAttribute](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2013/ms171833(v=vs.120)) +- [Designer Serialization Overview](https://msdn.microsoft.com/library/c342635a-aa5f-4281-915b-b013738af15a) +- [How to: Serialize Collections of Standard Types with the DesignerSerializationVisibilityAttribute](https://msdn.microsoft.com/library/7829fcdd-8205-405f-8231-a1282a9835c9) - [Walkthrough: Automatically Populating the Toolbox with Custom Components](../../../../docs/framework/winforms/controls/walkthrough-automatically-populating-the-toolbox-with-custom-components.md) diff --git a/docs/framework/winforms/controls/sort-and-filter-ado-net-data-with-wf-bindingsource-component.md b/docs/framework/winforms/controls/sort-and-filter-ado-net-data-with-wf-bindingsource-component.md index 53add6872ae65..77bb7a0466729 100644 --- a/docs/framework/winforms/controls/sort-and-filter-ado-net-data-with-wf-bindingsource-component.md +++ b/docs/framework/winforms/controls/sort-and-filter-ado-net-data-with-wf-bindingsource-component.md @@ -50,5 +50,5 @@ You can expose the sorting and filtering capability of - -- [How to: Install Sample Databases](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2013/8b6y4c7s(v=vs.120)) +- [How to: Install Sample Databases](https://msdn.microsoft.com/library/ed1291f6-604c-4972-ae22-0345c6dea12e) - [BindingSource Component](../../../../docs/framework/winforms/controls/bindingsource-component.md) diff --git a/docs/framework/winforms/controls/splitcontainer-control-overview-windows-forms.md b/docs/framework/winforms/controls/splitcontainer-control-overview-windows-forms.md index eeba393c85ab9..492116af701f4 100644 --- a/docs/framework/winforms/controls/splitcontainer-control-overview-windows-forms.md +++ b/docs/framework/winforms/controls/splitcontainer-control-overview-windows-forms.md @@ -46,4 +46,4 @@ The Windows Forms control can be thou ## See also - - [SplitContainer Control](../../../../docs/framework/winforms/controls/splitcontainer-control-windows-forms.md) -- [SplitContainer Control Sample](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2008/0ffz7d1b(v=vs.90)) +- [SplitContainer Control Sample](https://msdn.microsoft.com/library/9015fad0-7108-4d85-a83a-a72d038c4f65) diff --git a/docs/framework/winforms/controls/splitcontainer-control-windows-forms.md b/docs/framework/winforms/controls/splitcontainer-control-windows-forms.md index 8a8689811253a..b7a70cac8a7d2 100644 --- a/docs/framework/winforms/controls/splitcontainer-control-windows-forms.md +++ b/docs/framework/winforms/controls/splitcontainer-control-windows-forms.md @@ -27,7 +27,7 @@ The Windows Forms `SplitContainer` control can be thought of as a composite; it [How to: Create a Multipane User Interface with Windows Forms](../../../../docs/framework/winforms/controls/how-to-create-a-multipane-user-interface-with-windows-forms.md) Creates a multi-pane user interface that is similar to the one used in Microsoft Outlook. - Also see [How to: Split a Window Horizontally Using the Designer](how-to-split-a-window-horizontally-using-the-designer.md), [How to: Create a Windows Explorer–Style Interface on a Windows Form](how-to-create-a-windows-explorer-style-interface-on-a-windows-form.md), [How to: Create a Multipane User Interface with Windows Forms Using the Designer](create-a-multipane-user-interface-with-wf-using-the-designer.md). + Also see [How to: Split a Window Horizontally Using the Designer](how-to-split-a-window-horizontally-using-the-designer.md), [How to: Create a Windows Explorer–Style Interface on a Windows Form](https://msdn.microsoft.com/library/zh2fe5a5\(v=vs.110\)), [How to: Create a Multipane User Interface with Windows Forms Using the Designer](create-a-multipane-user-interface-with-wf-using-the-designer.md). ## Reference class diff --git a/docs/framework/winforms/controls/statusstrip-control-overview.md b/docs/framework/winforms/controls/statusstrip-control-overview.md index 1dc5421ea0e18..14f2db687b415 100644 --- a/docs/framework/winforms/controls/statusstrip-control-overview.md +++ b/docs/framework/winforms/controls/statusstrip-control-overview.md @@ -15,7 +15,7 @@ A control displays information about an There is extensive support for handling items and common commands in Visual Studio. - Also see [StatusStrip Items Collection Editor](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233631(v=vs.100)) and [StatusStrip Tasks Dialog Box](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233642(v=vs.100)). + Also see [StatusStrip Items Collection Editor](https://msdn.microsoft.com/library/ms233631\(v=vs.110\)), [StatusStrip Tasks Dialog Box](https://msdn.microsoft.com/library/ms233642\(v=vs.110\)). Although replaces and extends the control of previous versions, is retained for both backward compatibility and future use if you choose. diff --git a/docs/framework/winforms/controls/statusstrip-control.md b/docs/framework/winforms/controls/statusstrip-control.md index 7e4601165ccd1..a98b6305cb661 100644 --- a/docs/framework/winforms/controls/statusstrip-control.md +++ b/docs/framework/winforms/controls/statusstrip-control.md @@ -16,7 +16,7 @@ The Windows Forms `StatusStrip` control is used on forms as an area, usually dis [How to: Use the Spring Property Interactively in a StatusStrip](../../../../docs/framework/winforms/controls/how-to-use-the-spring-property-interactively-in-a-statusstrip.md) Demonstrates using the `Spring` property to interactively center a `ToolStripStatusLabel` in a `StatusStrip`. - Also see [StatusStrip Items Collection Editor](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233631(v=vs.100)) and [StatusStrip Tasks Dialog Box](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233642(v=vs.100)). + Also see [StatusStrip Items Collection Editor](https://msdn.microsoft.com/library/ms233631\(v=vs.110\)), [StatusStrip Items Collection Editor](https://msdn.microsoft.com/library/ms233642\(v=vs.110\)). ## Reference diff --git a/docs/framework/winforms/controls/tablelayoutpanel-control-overview.md b/docs/framework/winforms/controls/tablelayoutpanel-control-overview.md index d2f017d1e9e7b..a649f6941078e 100644 --- a/docs/framework/winforms/controls/tablelayoutpanel-control-overview.md +++ b/docs/framework/winforms/controls/tablelayoutpanel-control-overview.md @@ -33,7 +33,7 @@ The control arranges its contents i 3. [How to: Edit Columns and Rows in a TableLayoutPanel Control](how-to-edit-columns-and-rows-in-a-tablelayoutpanel-control.md) -4. [Walkthrough: Arranging Controls on Windows Forms Using a TableLayoutPanel](walkthrough-arranging-controls-on-windows-forms-using-a-tablelayoutpanel.md) +4. [Walkthrough: Arranging Controls on Windows Forms Using a TableLayoutPanel](https://msdn.microsoft.com/library/w4yc3e8c\(v=vs.110\)) ## See also - diff --git a/docs/framework/winforms/controls/tablelayoutpanel-control-windows-forms.md b/docs/framework/winforms/controls/tablelayoutpanel-control-windows-forms.md index 89aa6abc51e43..9ee2fed41b1c1 100644 --- a/docs/framework/winforms/controls/tablelayoutpanel-control-windows-forms.md +++ b/docs/framework/winforms/controls/tablelayoutpanel-control-windows-forms.md @@ -38,7 +38,7 @@ The control arranges its contents i 3. [How to: Edit Columns and Rows in a TableLayoutPanel Control](how-to-edit-columns-and-rows-in-a-tablelayoutpanel-control.md) -4. [Walkthrough: Arranging Controls on Windows Forms Using a TableLayoutPanel](walkthrough-arranging-controls-on-windows-forms-using-a-tablelayoutpanel.md) +4. [Walkthrough: Arranging Controls on Windows Forms Using a TableLayoutPanel](https://msdn.microsoft.com/library/w4yc3e8c\(v=vs.110\)) ## Reference @@ -54,4 +54,4 @@ The control arranges its contents i [Localization](../../../../docs/standard/globalization-localization/localization.md) Provides an overview of topics relating to localization. - Also see [Localizing Applications](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2013/z68135h5(v=vs.120)). + Also see [Localizing Applications](https://msdn.microsoft.com/library/z68135h5\(v=vs.110\)) or [Localizing Applications](https://msdn.microsoft.com/library/z68135h5\(v=vs.120\)) diff --git a/docs/framework/winforms/controls/timer-component-overview-windows-forms.md b/docs/framework/winforms/controls/timer-component-overview-windows-forms.md index 607d00fad0dda..d7be17a92e1bc 100644 --- a/docs/framework/winforms/controls/timer-component-overview-windows-forms.md +++ b/docs/framework/winforms/controls/timer-component-overview-windows-forms.md @@ -9,7 +9,7 @@ helpviewer_keywords: ms.assetid: e672c05b-a8b6-4b26-9e4d-9223aa9e3873 --- # Timer Component Overview (Windows Forms) -The Windows Forms is a component that raises an event at regular intervals. This component is designed for a Windows Forms environment. If you need a timer that is suitable for a server environment, see [Introduction to Server-Based Timers](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2008/tb9yt5e6(v=vs.90)). +The Windows Forms is a component that raises an event at regular intervals. This component is designed for a Windows Forms environment. If you need a timer that is suitable for a server environment, see [Introduction to Server-Based Timers](https://msdn.microsoft.com/library/adc0bc0a-a519-4812-bafc-fb9d1a5801fc). ## Key Properties, Methods, and Events The length of the intervals is defined by the property, whose value is in milliseconds. When the component is enabled, the event is raised every interval. This is where you would add code to be executed. For more information, see [How to: Run Procedures at Set Intervals with the Windows Forms Timer Component](../../../../docs/framework/winforms/controls/run-procedures-at-set-intervals-with-wf-timer-component.md). The key methods of the component are and , which turn the timer on and off. When the timer is switched off, it resets; there is no way to pause a component. diff --git a/docs/framework/winforms/controls/timer-component-windows-forms.md b/docs/framework/winforms/controls/timer-component-windows-forms.md index 4718707335c1d..3bac9e0266bcc 100644 --- a/docs/framework/winforms/controls/timer-component-windows-forms.md +++ b/docs/framework/winforms/controls/timer-component-windows-forms.md @@ -31,5 +31,5 @@ The Windows Forms is a component that raises a [Controls to Use on Windows Forms](../../../../docs/framework/winforms/controls/controls-to-use-on-windows-forms.md) Provides a complete list of Windows Forms controls, with links to information on their use. - [Timer Control for Visual Basic 6.0 Users](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2008/zffx82xt(v=vs.90)) + [Timer Control for Visual Basic 6.0 Users](https://msdn.microsoft.com/library/38e5184a-1e50-45cf-b936-dae566c0cfc5) Describes how timer functionality has changed in Visual Basic as compared to previous versions. diff --git a/docs/framework/winforms/controls/toolstrip-control-windows-forms.md b/docs/framework/winforms/controls/toolstrip-control-windows-forms.md index d90b4e0af0897..c755bce877213 100644 --- a/docs/framework/winforms/controls/toolstrip-control-windows-forms.md +++ b/docs/framework/winforms/controls/toolstrip-control-windows-forms.md @@ -67,7 +67,7 @@ ms.assetid: e5ef455a-e049-429c-8005-30c93132fb79 [How to: Implement a Custom ToolStripRenderer](../../../../docs/framework/winforms/controls/how-to-implement-a-custom-toolstriprenderer.md) Describes how to customize the appearance of a control by implementing a class that derives from . -- [How to: Create a Basic Windows Forms ToolStrip with Standard Items Using the Designer](create-a-basic-wf-toolstrip-with-standard-items-using-the-designer.md) +- [How to: Create a Basic Windows Forms ToolStrip with Standard Items Using the Designer](https://msdn.microsoft.com/library/571c1z99\(v=vs.110\)) - [How to: Move a ToolStrip Out of a ToolStripContainer onto a Form](how-to-move-a-toolstrip-out-of-a-toolstripcontainer-onto-a-form.md) @@ -75,9 +75,9 @@ ms.assetid: e5ef455a-e049-429c-8005-30c93132fb79 - [Walkthrough: Creating an MDI Form with Menu Merging and ToolStrip Controls](walkthrough-creating-an-mdi-form-with-menu-merging-and-toolstrip-controls.md) -- [ToolStrip Tasks Dialog Box](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233648(v=vs.100)) +- [ToolStrip Tasks Dialog Box](https://msdn.microsoft.com/library/ms233648\(v=vs.110\)) -- [ToolStrip Items Collection Editor](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233643(v=vs.100)) +- [ToolStrip Items Collection Editor](https://msdn.microsoft.com/library/ms233643\(v=vs.110\)) ## Reference class diff --git a/docs/framework/winforms/controls/toolstrip-technology-summary.md b/docs/framework/winforms/controls/toolstrip-technology-summary.md index af276b8d1606f..1578e73ab7fb4 100644 --- a/docs/framework/winforms/controls/toolstrip-technology-summary.md +++ b/docs/framework/winforms/controls/toolstrip-technology-summary.md @@ -57,26 +57,26 @@ This topic summarizes information about the `ToolStrip` control and the classes ### Task Dialog Boxes In Visual Studio, clicking the smart tag on a control in the designer displays a task list for convenient access to many frequently used commands. -- [MenuStrip Tasks Dialog Box](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233645(v=vs.100)) +- [MenuStrip Tasks Dialog Box](https://msdn.microsoft.com/library/ms233645\(v=vs.110\)) -- [ToolStrip Tasks Dialog Box](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233648(v=vs.100)) +- [ToolStrip Tasks Dialog Box](https://msdn.microsoft.com/library/ms233648\(v=vs.110\)) -- [ContextMenuStrip Tasks Dialog Box](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233646(v=vs.100)) +- [ContextMenuStrip Tasks Dialog Box](https://msdn.microsoft.com/library/ms233646\(v=vs.110\)) -- [StatusStrip Tasks Dialog Box](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233642(v=vs.100)) +- [StatusStrip Tasks Dialog Box](https://msdn.microsoft.com/library/ms233642\(v=vs.110\)) -- [ToolStripContainer Tasks Dialog Box](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233647(v=vs.100)) +- [ToolStripContainer Tasks Dialog Box](https://msdn.microsoft.com/library/ms233647\(v=vs.110\)) ### Items Collection Editors In Visual Studio, when you click **Edit Items** on the task list or right-click the control and select **Edit Items** in the shortcut menu, the collection editor for the control is displayed. Collection editors let you add, remove, and reorder items that the control contains. You can also view and change the properties for the control and the control's items. -- [MenuStrip Items Collection Editor](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233625(v=vs.100)) +- [MenuStrip Items Collection Editor](https://msdn.microsoft.com/library/ms233625\(v=vs.110\)) -- [StatusStrip Items Collection Editor](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233631(v=vs.100)) +- [StatusStrip Items Collection Editor](https://msdn.microsoft.com/library/ms233631\(v=vs.110\)) -- [ContextMenuStrip Items Collection Editor](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233641(v=vs.100)) +- [ContextMenuStrip Items Collection Editor](https://msdn.microsoft.com/library/ms233641\(v=vs.110\)) -- [ToolStrip Items Collection Editor](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233643(v=vs.100)) +- [ToolStrip Items Collection Editor](https://msdn.microsoft.com/library/ms233643\(v=vs.110\)) ## Hosting Controls The class provides built-in wrappers for , , and controls. You can also host any other existing or COM control in a . diff --git a/docs/framework/winforms/controls/toolstripcontainer-control.md b/docs/framework/winforms/controls/toolstripcontainer-control.md index 742699a334660..3c8c9d08c5e15 100644 --- a/docs/framework/winforms/controls/toolstripcontainer-control.md +++ b/docs/framework/winforms/controls/toolstripcontainer-control.md @@ -29,7 +29,7 @@ ms.assetid: 378fa5b4-38e1-46f4-8e5c-d0c19dcd0200 Provides reference documentation for the of a control. - Also see [ToolStripContainer Tasks Dialog Box](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/ms233647(v=vs.100)). + Also see [ToolStripContainer Tasks Dialog Box](https://msdn.microsoft.com/library/ms233647\(v=vs.110\)). ## Related Sections diff --git a/docs/framework/winforms/controls/toolstrippanel-control-overview.md b/docs/framework/winforms/controls/toolstrippanel-control-overview.md index 539ea6c17e9d2..a01d7b7b16567 100644 --- a/docs/framework/winforms/controls/toolstrippanel-control-overview.md +++ b/docs/framework/winforms/controls/toolstrippanel-control-overview.md @@ -25,4 +25,4 @@ A provides a single area for position ## See also - - -- [ToolStrip Sample](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2008/ms181005(v=vs.90)) +- [ToolStrip Sample](https://msdn.microsoft.com/library/b7352439-184a-4a3a-b2ad-07465d3af9ed) diff --git a/docs/framework/winforms/controls/troubleshooting-control-and-component-authoring.md b/docs/framework/winforms/controls/troubleshooting-control-and-component-authoring.md index 501321a3fadc1..850e000fbcde2 100644 --- a/docs/framework/winforms/controls/troubleshooting-control-and-component-authoring.md +++ b/docs/framework/winforms/controls/troubleshooting-control-and-component-authoring.md @@ -13,7 +13,7 @@ helpviewer_keywords: ms.assetid: e9c8c099-2271-4737-882f-50f336c7a55e --- # Troubleshooting Control and Component Authoring -This topic lists the following common problems that arise when developing components and controls. +This topic lists the following common problems that arise when developing components and controls. For more information, see [Programming with Components](https://msdn.microsoft.com/library/d4d4fcb4-e0b8-46b3-b679-7ee0026eb9e3). - Cannot Add Control to Toolbox @@ -106,5 +106,6 @@ This topic lists the following common problems that arise when developing compon - [Walkthrough: Automatically Populating the Toolbox with Custom Components](../../../../docs/framework/winforms/controls/walkthrough-automatically-populating-the-toolbox-with-custom-components.md) - [How to: Test the Run-Time Behavior of a UserControl](../../../../docs/framework/winforms/controls/how-to-test-the-run-time-behavior-of-a-usercontrol.md) - [Walkthrough: Debugging Custom Windows Forms Controls at Design Time](../../../../docs/framework/winforms/controls/walkthrough-debugging-custom-windows-forms-controls-at-design-time.md) -- [Component Authoring](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2013/5dya64wy(v=vs.120)) -- [Troubleshooting Design-Time Development](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2013/ms171843(v=vs.120)) +- [Component Authoring](https://msdn.microsoft.com/library/4a5a5e49-0378-4a31-83bc-24da0f1a727d) +- [Troubleshooting Design-Time Development](https://msdn.microsoft.com/library/e048d08e-fa7c-4be8-b238-4abaa199a0a6) +- [Programming with Components](https://msdn.microsoft.com/library/d4d4fcb4-e0b8-46b3-b679-7ee0026eb9e3) diff --git a/docs/framework/winforms/controls/unbound-column-to-a-data-bound-datagridview.md b/docs/framework/winforms/controls/unbound-column-to-a-data-bound-datagridview.md index 30e9d7ffa8a1b..c46a002163283 100644 --- a/docs/framework/winforms/controls/unbound-column-to-a-data-bound-datagridview.md +++ b/docs/framework/winforms/controls/unbound-column-to-a-data-bound-datagridview.md @@ -15,7 +15,7 @@ The data you display in the control wil The following code example demonstrates how to create an unbound column of **Details** buttons to display a child table related to a particular row in a parent table when you implement a master/detail scenario. To respond to button clicks, implement a event handler that displays a form containing the child table. - There is support for this task in Visual Studio. Also see [How to: Add and Remove Columns in the Windows Forms DataGridView Control Using the Designer](add-and-remove-columns-in-the-datagrid-using-the-designer.md). + There is support for this task in Visual Studio. Also see [How to: Add and Remove Columns in the Windows Forms DataGridView Control Using the Designer](https://msdn.microsoft.com/library/dyyesckz\(v=vs.110\)) ## Example [!code-csharp[System.Windows.Forms.DataGridViewMisc#010](../../../../samples/snippets/csharp/VS_Snippets_Winforms/System.Windows.Forms.DataGridViewMisc/CS/datagridviewmisc.cs#010)] diff --git a/docs/framework/winforms/controls/using-the-managed-html-document-object-model.md b/docs/framework/winforms/controls/using-the-managed-html-document-object-model.md index 115b72693bdf6..1eb5db4a22544 100644 --- a/docs/framework/winforms/controls/using-the-managed-html-document-object-model.md +++ b/docs/framework/winforms/controls/using-the-managed-html-document-object-model.md @@ -33,3 +33,6 @@ The managed HTML document object model (DOM) provides a wrapper based on the [!I ## Related Sections [WebBrowser Control](../../../../docs/framework/winforms/controls/webbrowser-control-windows-forms.md) + +## See also +- [About the DHTML Object Model](https://msdn.microsoft.com/library/default.asp?url=/workshop/author/om/doc_object.asp) diff --git a/docs/framework/winforms/controls/varieties-of-custom-controls.md b/docs/framework/winforms/controls/varieties-of-custom-controls.md index c33f73159f3f6..e74a27697a1f6 100644 --- a/docs/framework/winforms/controls/varieties-of-custom-controls.md +++ b/docs/framework/winforms/controls/varieties-of-custom-controls.md @@ -18,7 +18,7 @@ With the .NET Framework, you can develop and implement new controls. You can ext Deciding which kind of control to create can be confusing. This topic highlights the differences among the various kinds of controls from which you can inherit, and provides you with information about how to choose a particular kind of control for your project. > [!NOTE] -> For information about authoring a control to use on Web Forms, see [Developing Custom ASP.NET Server Controls](https://docs.microsoft.com/previous-versions/aspnet/zt27tfhy(v=vs.100)). +> For information about authoring a control to use on Web Forms, see [Developing Custom ASP.NET Server Controls](https://msdn.microsoft.com/library/fbe26c16-cff4-4089-b3dd-877411f0c0ef). ## Base Control Class The class is the base class for Windows Forms controls. It provides the infrastructure required for visual display in Windows Forms applications. @@ -98,11 +98,11 @@ With the .NET Framework, you can develop and implement new controls. You can ext ## Custom Design Experience If you need to implement a custom design-time experience, you can author your own designer. For composite controls, derive your custom designer class from the or the classes. For extended and custom controls, derive your custom designer class from the class. - Use the to associate your control with your designer. For more information, see [Extending Design-Time Support](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2013/37899azc(v=vs.120)) and [How to: Create a Windows Forms Control That Takes Advantage of Design-Time Features](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2013/307hck25(v=vs.120)). + Use the to associate your control with your designer. For more information, see [Extending Design-Time Support](https://msdn.microsoft.com/library/d6ac8a6a-42fd-4bc8-bf33-b212811297e2) and [How to: Create a Windows Forms Control That Takes Advantage of Design-Time Features](https://msdn.microsoft.com/library/8e0bad0e-56f3-43d2-bf63-a945c654d97c). ## See also - [Developing Custom Windows Forms Controls with the .NET Framework](../../../../docs/framework/winforms/controls/developing-custom-windows-forms-controls.md) - [How to: Develop a Simple Windows Forms Control](../../../../docs/framework/winforms/controls/how-to-develop-a-simple-windows-forms-control.md) - [Developing a Composite Windows Forms Control](../../../../docs/framework/winforms/controls/developing-a-composite-windows-forms-control.md) -- [Extending Design-Time Support](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2013/37899azc(v=vs.120)) -- [How to: Create a Windows Forms Control That Takes Advantage of Design-Time Features](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2013/307hck25(v=vs.120)) +- [Extending Design-Time Support](https://msdn.microsoft.com/library/d6ac8a6a-42fd-4bc8-bf33-b212811297e2) +- [How to: Create a Windows Forms Control That Takes Advantage of Design-Time Features](https://msdn.microsoft.com/library/8e0bad0e-56f3-43d2-bf63-a945c654d97c) diff --git a/docs/framework/winforms/controls/walkthrough-arranging-controls-on-windows-forms-using-snaplines.md b/docs/framework/winforms/controls/walkthrough-arranging-controls-on-windows-forms-using-snaplines.md index b4f280766badd..2b4d4fb9c4574 100644 --- a/docs/framework/winforms/controls/walkthrough-arranging-controls-on-windows-forms-using-snaplines.md +++ b/docs/framework/winforms/controls/walkthrough-arranging-controls-on-windows-forms-using-snaplines.md @@ -216,7 +216,7 @@ Precise placement of controls on your form is a high priority for many applicati #### To disable snaplines in the design environment -1. From the **Tools** menu, open the **Options** dialog box. Open the Windows Forms Designer dialog box. For details, see [General, Windows Forms Designer, Options Dialog Box](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/5aazxs78(v=vs.100)). +1. From the **Tools** menu, open the **Options** dialog box. Open the Windows Forms Designer dialog box. For details, see [General, Windows Forms Designer, Options Dialog Box](https://msdn.microsoft.com/library/8dd170af-72f0-4212-b04b-034ceee92834). 2. Select the **General** node. In the **Layout Mode** section, change the selection from **SnapLines** to **SnapToGrid**. diff --git a/docs/framework/winforms/controls/walkthrough-creating-a-professionally-styled-toolstrip-control.md b/docs/framework/winforms/controls/walkthrough-creating-a-professionally-styled-toolstrip-control.md index 01014e560d7ea..beab23e448a4c 100644 --- a/docs/framework/winforms/controls/walkthrough-creating-a-professionally-styled-toolstrip-control.md +++ b/docs/framework/winforms/controls/walkthrough-creating-a-professionally-styled-toolstrip-control.md @@ -43,7 +43,7 @@ You can give your application’s controls 2. In **Solution Explorer**, delete the project's default control by deleting the source file named "UserControl1.cs" or "UserControl1.vb", depending on your language of choice. - For more information, see [How to: Remove, Delete, and Exclude Items](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/0ebzhwsk(v=vs.100)). + For more information, see [NIB:How to: Remove, Delete, and Exclude Items](https://msdn.microsoft.com/library/6dffdc86-29c8-4eff-bcd8-e3a0dd9e9a73). 3. Add a new item to the **StackViewLibrary** project. Give the new source file a base name of `StackView`. @@ -115,7 +115,7 @@ You can give your application’s controls 8. Rename the `mailStackButton_Click` event handler to `stackButton_Click`. - For more information, see [Rename a code symbol refactoring](/visualstudio/ide/reference/rename). + For more information, see [How to: Rename an Identifier (Visual Basic)](https://msdn.microsoft.com/library/e5a5edf8-3dba-4119-81f4-fc2aba180e0c). 9. Insert the following code into the `stackButton_Click` event handler. @@ -129,7 +129,7 @@ You can give your application’s controls 12. Repeat steps 10 and 11 for the `contactsStackButton` and `tasksStackButton` controls. ## Defining Icons - Each `StackView` button has an associated icon. For convenience, each icon is represented as a Base64-encoded string, which is deserialized before a is created from it. In a production environment, you store bitmap data as a resource, and your icons appear in the Windows Forms Designer. For more information, see [How to: Add Background Images to Windows Forms](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/dff9f95f(v=vs.100)). + Each `StackView` button has an associated icon. For convenience, each icon is represented as a Base64-encoded string, which is deserialized before a is created from it. In a production environment, you store bitmap data as a resource, and your icons appear in the Windows Forms Designer. For more information, see [How to: Add Background Images to Windows Forms](https://msdn.microsoft.com/library/7a509ba2-055c-4ae6-b88a-54625c6d9aff). #### To define icons From 8b48842a47d77fafa08f1d4db629b384c7ab509a Mon Sep 17 00:00:00 2001 From: Dennis Lee Date: Thu, 21 Feb 2019 15:48:41 -0800 Subject: [PATCH 3/5] Another 18 files with MSDN link fixes. --- .../winforms/windows-forms-data-binding.md | 2 +- .../winforms/windows-forms-security.md | 10 +++---- .../wpf/advanced/annotations-overview.md | 2 +- .../wpf/advanced/commanding-overview.md | 2 +- .../wpf/advanced/drawing-formatted-text.md | 4 +-- .../wpf/advanced/graphics-rendering-tiers.md | 6 ++--- .../wpf/advanced/handwriting-recognition.md | 4 +-- .../how-to-analyze-ink-with-analysis-hints.md | 4 +-- .../how-to-use-a-thicknessconverter-object.md | 4 +-- .../wpf/advanced/printing-how-to-topics.md | 3 --- .../wpf/advanced/printing-overview.md | 12 ++++----- ...-model-windows-forms-and-com-versus-wpf.md | 26 +++++++++---------- docs/framework/wpf/advanced/trees-in-wpf.md | 2 +- .../troubleshooting-hybrid-applications.md | 2 +- ...-binding-to-data-in-hybrid-applications.md | 2 +- ...h-creating-your-first-touch-application.md | 2 +- ...nabling-drag-and-drop-on-a-user-control.md | 2 +- ...-wpf-composite-control-in-windows-forms.md | 2 +- 18 files changed, 44 insertions(+), 47 deletions(-) diff --git a/docs/framework/winforms/windows-forms-data-binding.md b/docs/framework/winforms/windows-forms-data-binding.md index 0d97799a2bcf0..220e5fbe9ae2c 100644 --- a/docs/framework/winforms/windows-forms-data-binding.md +++ b/docs/framework/winforms/windows-forms-data-binding.md @@ -45,7 +45,7 @@ Data binding in Windows Forms gives you the means to display and make changes to [How to: Ensure the Selected Row in a Child Table Remains at the Correct Position](../../../docs/framework/winforms/ensure-the-selected-row-in-a-child-table-correct.md) Shows how to ensure the selected row of a child table does not change, when a change is made to a field of the parent table. - Also see [Interfaces Related to Data Binding](https://msdn.microsoft.com/library/41e17s4b\(v=vs.110\)), [How to: Navigate Data in Windows Forms](https://msdn.microsoft.com/library/b63ha24w\(v=vs.110\)), [How to: Create a Simple-Bound Control on a Windows Form](https://msdn.microsoft.com/library/sw223a62\(v=vs.110\)). + Also see [Interfaces Related to Data Binding](interfaces-related-to-data-binding.md), [How to: Navigate Data in Windows Forms](how-to-navigate-data-in-windows-forms.md), and [How to: Create a Simple-Bound Control on a Windows Form](how-to-create-a-simple-bound-control-on-a-windows-form.md). ## Reference diff --git a/docs/framework/winforms/windows-forms-security.md b/docs/framework/winforms/windows-forms-security.md index 753f8f8fad610..738e402b73ad1 100644 --- a/docs/framework/winforms/windows-forms-security.md +++ b/docs/framework/winforms/windows-forms-security.md @@ -27,10 +27,10 @@ Windows Forms features a security model that is code-based (security levels are Describes performing window manipulation, using the Clipboard, and making calls to unmanaged code in a semi-trusted environment. ## Related Sections - [NIB: Default Security Policy](https://msdn.microsoft.com/library/2c086873-0894-4f4d-8f7e-47427c1a3b55) + [Default Security Policy](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/03kwzyfc(v=vs.100)) Lists the default permissions granted in the Full Trust, Local Intranet, and Internet permission sets. - [NIB: General Security Policy Administration](https://msdn.microsoft.com/library/5121fe35-f0e3-402c-94ab-4f35b0a87b4b) + [General Security Policy Administration](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/ed5htz45(v=vs.100)) Gives information about the administering the .NET Framework security policy and elevating permissions. [Dangerous Permissions and Policy Administration](../../../docs/framework/misc/dangerous-permissions-and-policy-administration.md) @@ -39,7 +39,7 @@ Windows Forms features a security model that is code-based (security levels are [Secure Coding Guidelines](../../../docs/standard/security/secure-coding-guidelines.md) Links to topics that explain the best practices for securely writing code against the .NET Framework. - [NIB: Requesting Permissions](https://msdn.microsoft.com/library/0447c49d-8cba-45e4-862c-ff0b59bebdc2) + [Requesting Permissions](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/yd267cce(v=vs.100)) Discusses the use of attributes to let the runtime know what permissions your code needs to run. [Key Security Concepts](../../../docs/standard/security/key-security-concepts.md) @@ -48,8 +48,8 @@ Windows Forms features a security model that is code-based (security levels are [Code Access Security Basics](../../../docs/framework/misc/code-access-security-basics.md) Discusses the basics of working with the .NET Framework run time security policy. - [NIB: Determining When to Modify Security Policy](https://msdn.microsoft.com/library/af749b17-e461-409d-84b9-a3d44789db16) + [Determining When to Modify Security Policy](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/xky659fc(v=vs.100)) Explains how to determine when your applications need to diverge from the default security policy. - [NIB: Deploying Security Policy](https://msdn.microsoft.com/library/f936c1e5-033b-4bd9-a3bd-a39ba733a681) + [Deploying Security Policy](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/13wcxx6y(v=vs.100)) Discusses the best manner for deploying security policy changes. diff --git a/docs/framework/wpf/advanced/annotations-overview.md b/docs/framework/wpf/advanced/annotations-overview.md index d3824b92107d2..477d0bd4b119c 100644 --- a/docs/framework/wpf/advanced/annotations-overview.md +++ b/docs/framework/wpf/advanced/annotations-overview.md @@ -69,4 +69,4 @@ Writing notes or comments on paper documents is such a commonplace activity that - [ContextMenu Overview](../../../../docs/framework/wpf/controls/contextmenu-overview.md) - [Commanding Overview](../../../../docs/framework/wpf/advanced/commanding-overview.md) - [Flow Document Overview](../../../../docs/framework/wpf/advanced/flow-document-overview.md) -- [How to: Add a Command to a MenuItem](https://msdn.microsoft.com/library/013d68a0-5373-4a68-bd91-5de574307370) +- [How to: Add a Command to a MenuItem](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms741839(v=vs.90)) diff --git a/docs/framework/wpf/advanced/commanding-overview.md b/docs/framework/wpf/advanced/commanding-overview.md index 3746774fe53e8..a52fac4d37dcd 100644 --- a/docs/framework/wpf/advanced/commanding-overview.md +++ b/docs/framework/wpf/advanced/commanding-overview.md @@ -185,5 +185,5 @@ ms.assetid: bc208dfe-367d-426a-99de-52b7e7511e81 - [Input Overview](../../../../docs/framework/wpf/advanced/input-overview.md) - [Routed Events Overview](../../../../docs/framework/wpf/advanced/routed-events-overview.md) - [Implement ICommandSource](../../../../docs/framework/wpf/advanced/how-to-implement-icommandsource.md) -- [How to: Add a Command to a MenuItem](https://msdn.microsoft.com/library/013d68a0-5373-4a68-bd91-5de574307370) +- [How to: Add a Command to a MenuItem](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms741839(v=vs.90)) - [Create a Custom RoutedCommand Sample](https://github.com/Microsoft/WPF-Samples/tree/master/Input%20and%20Commands/CustomRoutedCommand) diff --git a/docs/framework/wpf/advanced/drawing-formatted-text.md b/docs/framework/wpf/advanced/drawing-formatted-text.md index 5f3c6b54bb680..1831447cdeddd 100644 --- a/docs/framework/wpf/advanced/drawing-formatted-text.md +++ b/docs/framework/wpf/advanced/drawing-formatted-text.md @@ -79,7 +79,7 @@ Example of an image brush applied to the stroke and highlight ![Sphere following the path geometry of text](../../../../docs/framework/wpf/advanced/media/textpathgeometry01.gif "TextPathGeometry01") Sphere following the path geometry of text - For more information, see [How to: Create a PathGeometry Animation for Text](https://msdn.microsoft.com/library/29f8051e-798a-463f-a926-a099a99e9c67). + For more information, see [How to: Create a PathGeometry Animation for Text](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/ms743610(v=vs.100)). You can create other interesting uses for formatted text once it has been converted to a object. For example, you can clip video to display inside it. @@ -122,4 +122,4 @@ Video displaying in the path geometry of text - [Documents in WPF](../../../../docs/framework/wpf/advanced/documents-in-wpf.md) - [Typography in WPF](../../../../docs/framework/wpf/advanced/typography-in-wpf.md) - [Create Outlined Text](../../../../docs/framework/wpf/advanced/how-to-create-outlined-text.md) -- [How to: Create a PathGeometry Animation for Text](https://msdn.microsoft.com/library/29f8051e-798a-463f-a926-a099a99e9c67) +- [How to: Create a PathGeometry Animation for Text](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/ms743610(v=vs.100)) diff --git a/docs/framework/wpf/advanced/graphics-rendering-tiers.md b/docs/framework/wpf/advanced/graphics-rendering-tiers.md index 8e86686bf253c..53a2aa2c07e15 100644 --- a/docs/framework/wpf/advanced/graphics-rendering-tiers.md +++ b/docs/framework/wpf/advanced/graphics-rendering-tiers.md @@ -84,7 +84,7 @@ A rendering tier defines a level of graphics hardware capability and performance |Rasterized content that uses |Any content rendered by using the method of .| |Tiled content that uses |Any tiled content in which the property of the is set to .| |Surfaces that exceed the maximum texture size of the graphics hardware|For most graphics hardware, large surfaces are 2048x2048 or 4096x4096 pixels in size.| -|Any operation whose video RAM requirement exceeds the memory of the graphics hardware|You can monitor application video RAM usage by using the Perforator tool that is included in the [WPF Performance Suite](https://msdn.microsoft.com/library/67cafaad-57ad-4ecb-9c08-57fac144393e) in the Windows SDK.| +|Any operation whose video RAM requirement exceeds the memory of the graphics hardware|You can monitor application video RAM usage by using the Perforator tool that is included in the [WPF Performance Suite](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/aa969767(v=vs.100)) in the Windows SDK.| |Layered windows|Layered windows allow [!INCLUDE[TLA2#tla_winclient](../../../../includes/tla2sharptla-winclient-md.md)] applications to render content to the screen in a non-rectangular window. On operating systems that support Windows Display Driver Model (WDDM), such as [!INCLUDE[TLA2#tla_winvista](../../../../includes/tla2sharptla-winvista-md.md)] and [!INCLUDE[win7](../../../../includes/win7-md.md)], layered windows are hardware accelerated. On other systems, such as [!INCLUDE[winxp](../../../../includes/winxp-md.md)], layered windows are rendered by software with no hardware acceleration.

You can enable layered windows in [!INCLUDE[TLA2#tla_winclient](../../../../includes/tla2sharptla-winclient-md.md)] by setting the following properties:

- =
- = `true`
- = | @@ -111,7 +111,7 @@ A rendering tier defines a level of graphics hardware capability and performance |Perforator|Use for analyzing rendering behavior.| |Visual Profiler|Use for profiling the use of [!INCLUDE[TLA2#tla_winclient](../../../../includes/tla2sharptla-winclient-md.md)] services, such as layout and event handling, by elements in the visual tree.| - The WPF Performance Suite provides a rich, graphical view of performance data. For more information about WPF performance tools, see [WPF Performance Suite](https://msdn.microsoft.com/library/67cafaad-57ad-4ecb-9c08-57fac144393e). + The WPF Performance Suite provides a rich, graphical view of performance data. For more information about WPF performance tools, see [WPF Performance Suite](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/aa969767(v=vs.100)). ### DirectX Diagnostic Tool The [!INCLUDE[TLA2#tla_dx](../../../../includes/tla2sharptla-dx-md.md)] Diagnostic Tool, Dxdiag.exe, is designed to help you troubleshoot [!INCLUDE[TLA2#tla_dx](../../../../includes/tla2sharptla-dx-md.md)]-related issues. The default installation folder for the [!INCLUDE[TLA2#tla_dx](../../../../includes/tla2sharptla-dx-md.md)] Diagnostic Tool is: @@ -127,6 +127,6 @@ DirectX Diagnostic Tool main window - - - [Optimizing WPF Application Performance](../../../../docs/framework/wpf/advanced/optimizing-wpf-application-performance.md) -- [WPF Performance Suite](https://msdn.microsoft.com/library/67cafaad-57ad-4ecb-9c08-57fac144393e) +- [WPF Performance Suite](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/aa969767(v=vs.100)) - [Graphics Rendering Registry Settings](../../../../docs/framework/wpf/graphics-multimedia/graphics-rendering-registry-settings.md) - [Animation Tips and Tricks](../../../../docs/framework/wpf/graphics-multimedia/animation-tips-and-tricks.md) diff --git a/docs/framework/wpf/advanced/handwriting-recognition.md b/docs/framework/wpf/advanced/handwriting-recognition.md index fcb6ebf139756..f1488655740f4 100644 --- a/docs/framework/wpf/advanced/handwriting-recognition.md +++ b/docs/framework/wpf/advanced/handwriting-recognition.md @@ -13,7 +13,7 @@ ms.assetid: f4e8576d-e731-4bac-9818-22e2ae636636 This section discusses the fundamentals of recognition as it pertains to digital ink in the WPF platform. ## Recognition Solutions - The following example shows how to recognize ink using the [Microsoft.Ink.InkCollector](https://msdn.microsoft.com/library/microsoft.ink.inkcollector\(v=vs.90\).aspx) class. + The following example shows how to recognize ink using the [Microsoft.Ink.InkCollector](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms583683(v=vs.90)) class. > [!NOTE] > This sample requires that handwriting recognizers be installed on the system. @@ -28,4 +28,4 @@ This section discusses the fundamentals of recognition as it pertains to digital [!code-vb[InkRecognition#2](../../../../samples/snippets/visualbasic/VS_Snippets_Wpf/InkRecognition/VisualBasic/Window1.xaml.vb#2)] ## See also -- [Microsoft.Ink.InkCollector](https://msdn.microsoft.com/library/microsoft.ink.inkcollector\(v=vs.90\).aspx) +- [Microsoft.Ink.InkCollector](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms583683(v=vs.90)) diff --git a/docs/framework/wpf/advanced/how-to-analyze-ink-with-analysis-hints.md b/docs/framework/wpf/advanced/how-to-analyze-ink-with-analysis-hints.md index 204e04a276322..c98333a0c0acf 100644 --- a/docs/framework/wpf/advanced/how-to-analyze-ink-with-analysis-hints.md +++ b/docs/framework/wpf/advanced/how-to-analyze-ink-with-analysis-hints.md @@ -12,10 +12,10 @@ helpviewer_keywords: ms.assetid: d4421ed4-77f5-4640-829e-9f1de50b2ff2 --- # How to: Analyze Ink with Analysis Hints -An [System.Windows.Ink.AnalysisHintNode](https://msdn.microsoft.com/library/system.windows.ink.analysishintnode(v=vs.100).aspx) provides a hint for the [System.Windows.Ink.InkAnalyzer](https://msdn.microsoft.com/library/system.windows.ink.inkanalyzer(v=vs.100).aspx) to which it is attached. The hint applies to the area specified by the [System.Windows.Ink.ContextNode.Location%2A](https://msdn.microsoft.com/library/system.windows.ink.contextnode.location(v=vs.100).aspx) property of the [System.Windows.Ink.AnalysisHintNode](https://msdn.microsoft.com/library/system.windows.ink.analysishintnode(v=vs.100).aspx) and provides extra context to the ink analyzer to improve recognition accuracy. The [System.Windows.Ink.InkAnalyzer](https://msdn.microsoft.com/library/system.windows.ink.inkanalyzer(v=vs.100).aspx) applies this context information when analyzing ink obtained from within the hint's area. +An [System.Windows.Ink.AnalysisHintNode](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms610344(v=vs.90)) provides a hint for the [System.Windows.Ink.InkAnalyzer](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms616754(v=vs.90)) to which it is attached. The hint applies to the area specified by the [System.Windows.Ink.ContextNode.Location%2A](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms594508(v=vs.90)) property of the [System.Windows.Ink.AnalysisHintNode](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms610344(v=vs.90)) and provides extra context to the ink analyzer to improve recognition accuracy. The [System.Windows.Ink.InkAnalyzer](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms616754(v=vs.90)) applies this context information when analyzing ink obtained from within the hint's area. ## Example - The following example is an application that uses multiple [System.Windows.Ink.AnalysisHintNode](https://msdn.microsoft.com/library/system.windows.ink.analysishintnode(v=vs.100).aspx) objects on a form that accepts ink input. The application uses the [System.Windows.Ink.AnalysisHintNode.Factoid%2A](https://msdn.microsoft.com/library/system.windows.ink.analysishintnode.factoid(v=vs.100)) property to provide context information for each entry on the form. The application uses background analysis to analyze the ink and clears the form of all ink five seconds after the user stops adding ink. + The following example is an application that uses multiple [System.Windows.Ink.AnalysisHintNode](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms610344(v=vs.90)) objects on a form that accepts ink input. The application uses the [System.Windows.Ink.AnalysisHintNode.Factoid%2A](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms594341(v=vs.90)) property to provide context information for each entry on the form. The application uses background analysis to analyze the ink and clears the form of all ink five seconds after the user stops adding ink. [!code-xaml[HowToAnalyzeInk#1](../../../../samples/snippets/csharp/VS_Snippets_Wpf/HowToAnalyzeInk/CSharp/FormAnalyzer.xaml#1)] diff --git a/docs/framework/wpf/advanced/how-to-use-a-thicknessconverter-object.md b/docs/framework/wpf/advanced/how-to-use-a-thicknessconverter-object.md index 9c5fb17765c46..a037d4ee08c49 100644 --- a/docs/framework/wpf/advanced/how-to-use-a-thicknessconverter-object.md +++ b/docs/framework/wpf/advanced/how-to-use-a-thicknessconverter-object.md @@ -24,6 +24,6 @@ ms.assetid: 52682194-d7fd-499c-8005-73fcc84e7b2c - - - -- [How to: Change the Margin Property](https://msdn.microsoft.com/library/8a313efd-5f99-4097-b4c1-8fa49d8379a2) -- [How to: Convert a ListBoxItem to a new Data Type](https://msdn.microsoft.com/library/7a080b88-184e-4b27-bb61-d42bafba9727) +- [How to: Change the Margin Property](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms750561(v=vs.90)) +- [How to: Convert a ListBoxItem to a new Data Type](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms749147(v=vs.90)) - [Panels Overview](../../../../docs/framework/wpf/controls/panels-overview.md) diff --git a/docs/framework/wpf/advanced/printing-how-to-topics.md b/docs/framework/wpf/advanced/printing-how-to-topics.md index 63445a13167c8..92704c11e8550 100644 --- a/docs/framework/wpf/advanced/printing-how-to-topics.md +++ b/docs/framework/wpf/advanced/printing-how-to-topics.md @@ -25,9 +25,6 @@ The topics in this section demonstrate how to use the printing and print system [Enumerate a Subset of Print Queues](../../../../docs/framework/wpf/advanced/how-to-enumerate-a-subset-of-print-queues.md) Instructions for generating a list of printers having certain characteristics. - [NOTINBUILD: How to: Extend the Print Schema and Create New Print System Classes](https://msdn.microsoft.com/library/a3600218-1ea5-478a-9853-6560464f2885) - Extended discussion of how managed code programmers can extend the Print Schema to specialty printing devices or printers with new or uncommon features. - [Get Print System Object Properties Without Reflection](../../../../docs/framework/wpf/advanced/how-to-get-print-system-object-properties-without-reflection.md) Instructions for how to discover at runtime print system object's properties and their types. diff --git a/docs/framework/wpf/advanced/printing-overview.md b/docs/framework/wpf/advanced/printing-overview.md index 6fa7d9826d80c..9977198f65561 100644 --- a/docs/framework/wpf/advanced/printing-overview.md +++ b/docs/framework/wpf/advanced/printing-overview.md @@ -25,13 +25,13 @@ With Microsoft .NET Framework, application developers using Windows Presentation ## About XPS [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] is an electronic document format, a spool file format and a page description language. It is an open document format that uses [!INCLUDE[TLA#tla_xml](../../../../includes/tlasharptla-xml-md.md)], [!INCLUDE[TLA#tla_opc](../../../../includes/tlasharptla-opc-md.md)], and other industry standards to create cross-platform documents. [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] simplifies the process by which digital documents are created, shared, printed, viewed, and archived. For additional information on [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)], see [XPS Documents](/windows/desktop/printdocs/documents). - Several techniques for printing [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] based content using [!INCLUDE[TLA2#tla_wpf](../../../../includes/tla2sharptla-wpf-md.md)] are demonstrated in [Programmatically Print XPS Files](../../../../docs/framework/wpf/advanced/how-to-programmatically-print-xps-files.md). You may find it useful to reference these samples during review of content contained in this topic. (Unmanaged code developers should see documentation for the [MXDC_ESCAPE function](https://msdn.microsoft.com/library/windows/desktop/dd162739.aspx). Windows Forms developers must use the [!INCLUDE[TLA2#tla_api](../../../../includes/tla2sharptla-api-md.md)] in the namespace which does not support the full [!INCLUDE[TLA2#tla_xps](../../../../includes/tla2sharptla-xps-md.md)] print path, but does support a hybrid GDI-to-XPS print path. See **Print Path Architecture** below.) + Several techniques for printing [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] based content using [!INCLUDE[TLA2#tla_wpf](../../../../includes/tla2sharptla-wpf-md.md)] are demonstrated in [Programmatically Print XPS Files](../../../../docs/framework/wpf/advanced/how-to-programmatically-print-xps-files.md). You may find it useful to reference these samples during review of content contained in this topic. (Unmanaged code developers should see documentation for the [MXDC_ESCAPE function](/windows/desktop/printdocs/mxdc-escape). Windows Forms developers must use the [!INCLUDE[TLA2#tla_api](../../../../includes/tla2sharptla-api-md.md)] in the namespace which does not support the full [!INCLUDE[TLA2#tla_xps](../../../../includes/tla2sharptla-xps-md.md)] print path, but does support a hybrid GDI-to-XPS print path. See **Print Path Architecture** below.) ## XPS Print Path The [!INCLUDE[TLA#tla_metro](../../../../includes/tlasharptla-metro-md.md)] print path is a new [!INCLUDE[TLA#tla_mswin](../../../../includes/tlasharptla-mswin-md.md)] feature that redefines how printing is handled in Windows applications. Because [!INCLUDE[TLA2#tla_xps](../../../../includes/tla2sharptla-xps-md.md)] can replace a document presentation language (such as RTF), a print spooler format (such as WMF), and a page description language (such as PCL or Postscript); the new print path maintains the [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] format from application publication to the final processing in the print driver or device. - The [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] print path is built upon the [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] printer driver model (XPSDrv), which provides several benefits for developers such as [!INCLUDE[TLA#tla_wys](../../../../includes/tlasharptla-wys-md.md)] printing, improved color support, and significantly improved print performance. (For more on XPSDrv, see the [Windows Driver Development Kit](https://msdn.microsoft.com/library/windows/hardware/ff557573.aspx).) + The [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] print path is built upon the [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] printer driver model (XPSDrv), which provides several benefits for developers such as [!INCLUDE[TLA#tla_wys](../../../../includes/tlasharptla-wys-md.md)] printing, improved color support, and significantly improved print performance. (For more on XPSDrv, see the [Windows Driver Kit documentation](/windows-hardware/drivers/).) The operation of the print spooler for [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] documents is essentially the same as in previous versions of Windows. However, it has been enhanced to support the [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] print path in addition to the existing [!INCLUDE[TLA2#tla_gdi](../../../../includes/tla2sharptla-gdi-md.md)] print path. The new print path natively consumes an [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] spool file. While user-mode printer drivers written for previous versions of [!INCLUDE[TLA#tla_mswin](../../../../includes/tlasharptla-mswin-md.md)] will continue to work, an [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] printer driver (XPSDrv) is required in order to use the [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] print path. @@ -51,7 +51,7 @@ With Microsoft .NET Framework, application developers using Windows Presentation - Print Schema. The public schema is updated regularly and enables rapid extension of device capabilities. (See **PrintTicket and PrintCapabilities** below.) -- Extensible Filter Pipeline. The [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] printer driver (XPSDrv) filter pipeline was designed to enable both direct and scalable printing of [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] documents. (Lookup "XPSDrv" in the [Windows Driver Kit](https://msdn.microsoft.com/library/windows/hardware/ff557573.aspx).) +- Extensible Filter Pipeline. The [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] printer driver (XPSDrv) filter pipeline was designed to enable both direct and scalable printing of [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] documents. (Look up "XPSDrv" in the [Windows Driver Kit documentation](/windows-hardware/drivers/).) ### Print Path Architecture While both [!INCLUDE[TLA2#tla_win32](../../../../includes/tla2sharptla-win32-md.md)] and .NET Framework applications support [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)], [!INCLUDE[TLA2#tla_win32](../../../../includes/tla2sharptla-win32-md.md)] and Windows Forms applications use a [!INCLUDE[TLA2#tla_gdi](../../../../includes/tla2sharptla-gdi-md.md)] to [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] conversion in order to create [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] formatted content for the [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] printer driver (XPSDrv). These applications are not required to use the [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] print path, and can continue to use [!INCLUDE[TLA#tla_emf](../../../../includes/tlasharptla-emf-md.md)] based printing. However, most [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] features and enhancements are only available to applications that target the [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] print path. @@ -100,11 +100,11 @@ With Microsoft .NET Framework, application developers using Windows Presentation ## GDI Print Path - While [!INCLUDE[TLA2#tla_wpf](../../../../includes/tla2sharptla-wpf-md.md)] applications natively support the [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] print path, [!INCLUDE[TLA2#tla_win32](../../../../includes/tla2sharptla-win32-md.md)] and Windows Forms applications can also take advantage of some [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] features. The [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] printer driver (XPSDrv) can convert [!INCLUDE[TLA2#tla_gdi](../../../../includes/tla2sharptla-gdi-md.md)] based output to [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] format. For advanced scenarios, custom conversion of content is supported using the [Microsoft XPS Document Converter (MXDC)](https://msdn.microsoft.com/library/windows/desktop/ff686803.aspx). Similarly, [!INCLUDE[TLA2#tla_wpf](../../../../includes/tla2sharptla-wpf-md.md)] applications can also output to the [!INCLUDE[TLA2#tla_gdi](../../../../includes/tla2sharptla-gdi-md.md)] print path by calling one of the or methods of the class and designating a non-XpsDrv printer as the target print queue. + While [!INCLUDE[TLA2#tla_wpf](../../../../includes/tla2sharptla-wpf-md.md)] applications natively support the [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] print path, [!INCLUDE[TLA2#tla_win32](../../../../includes/tla2sharptla-win32-md.md)] and Windows Forms applications can also take advantage of some [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] features. The [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] printer driver (XPSDrv) can convert [!INCLUDE[TLA2#tla_gdi](../../../../includes/tla2sharptla-gdi-md.md)] based output to [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] format. For advanced scenarios, custom conversion of content is supported using the [Microsoft XPS Document Converter (MXDC)](/windows/desktop/printdocs/microsoft-xps-document-converter--mxdc-). Similarly, [!INCLUDE[TLA2#tla_wpf](../../../../includes/tla2sharptla-wpf-md.md)] applications can also output to the [!INCLUDE[TLA2#tla_gdi](../../../../includes/tla2sharptla-gdi-md.md)] print path by calling one of the or methods of the class and designating a non-XpsDrv printer as the target print queue. For applications that do not require [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] functionality or support, the current [!INCLUDE[TLA2#tla_gdi](../../../../includes/tla2sharptla-gdi-md.md)] print path remains unchanged. -- For additional reference material on the [!INCLUDE[TLA2#tla_gdi](../../../../includes/tla2sharptla-gdi-md.md)] print path and the various [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] conversion options, see [Microsoft XPS Document Converter (MXDC)](https://msdn.microsoft.com/library/windows/desktop/ff686803.aspx) and "XPSDrv" in the [Windows Driver Kit](https://msdn.microsoft.com/library/windows/hardware/ff557573.aspx). +- For additional reference material on the [!INCLUDE[TLA2#tla_gdi](../../../../includes/tla2sharptla-gdi-md.md)] print path and the various [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] conversion options, see [Microsoft XPS Document Converter (MXDC)](/windows/desktop/printdocs/microsoft-xps-document-converter--mxdc-) and "XPSDrv" in the [Windows Driver Kit documentation](/windows-hardware/drivers/). ## XPSDrv Driver Model @@ -140,4 +140,4 @@ For applications that do not require [!INCLUDE[TLA2#tla_metro](../../../../inclu - [Documents in WPF](../../../../docs/framework/wpf/advanced/documents-in-wpf.md) - [XPS Documents](/windows/desktop/printdocs/documents) - [Document Serialization and Storage](../../../../docs/framework/wpf/advanced/document-serialization-and-storage.md) -- [Microsoft XPS Document Converter (MXDC)](https://msdn.microsoft.com/library/windows/desktop/ff686803.aspx) +- [Microsoft XPS Document Converter (MXDC)](/windows/desktop/printdocs/microsoft-xps-document-converter--mxdc-) diff --git a/docs/framework/wpf/advanced/the-ink-object-model-windows-forms-and-com-versus-wpf.md b/docs/framework/wpf/advanced/the-ink-object-model-windows-forms-and-com-versus-wpf.md index d573d3c2a5375..dc5bbb6c7145b 100644 --- a/docs/framework/wpf/advanced/the-ink-object-model-windows-forms-and-com-versus-wpf.md +++ b/docs/framework/wpf/advanced/the-ink-object-model-windows-forms-and-com-versus-wpf.md @@ -18,7 +18,7 @@ ms.assetid: 577835be-b145-4226-8570-1d309e9b3901 There are essentially three platforms that support digital ink: the Tablet PC Windows Forms platform, the Tablet PC COM platform, and the Windows Presentation Foundation (WPF) platform. The Windows Forms and COM platforms share a similar object model, but the object model for the [!INCLUDE[TLA2#tla_wpf](../../../../includes/tla2sharptla-wpf-md.md)] platform is substantially different. This topic discusses the differences at a high-level so that developers that have worked with one object model can better understand the other. ## Enabling Ink in an Application - All three platforms ship objects and controls that enable an application to receive input from a tablet pen. The Windows Forms and COM platforms ship with [Microsoft.Ink.InkPicture](https://msdn.microsoft.com/library/aa514604.aspx), [Microsoft.Ink.InkEdit](https://msdn.microsoft.com/library/ms835842.aspx), [Microsoft.Ink.InkOverlay](https://msdn.microsoft.com/library/ms833057.aspx) and [Microsoft.Ink.InkCollector](https://msdn.microsoft.com/library/ms836493.aspx) classes. [Microsoft.Ink.InkPicture](https://msdn.microsoft.com/library/aa514604.aspx) and [Microsoft.Ink.InkEdit](https://msdn.microsoft.com/library/ms835842.aspx) are controls that you can add to an application to collect ink. The [Microsoft.Ink.InkOverlay](https://msdn.microsoft.com/library/ms833057.aspx) and [Microsoft.Ink.InkCollector](https://msdn.microsoft.com/library/ms836493.aspx) can be attached to an existing window to ink-enable windows and custom controls. + All three platforms ship objects and controls that enable an application to receive input from a tablet pen. The Windows Forms and COM platforms ship with [Microsoft.Ink.InkPicture](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms583740(v=vs.90)), [Microsoft.Ink.InkEdit](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms552265(v=vs.90)), [Microsoft.Ink.InkOverlay](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms552322(v=vs.90)) and [Microsoft.Ink.InkCollector](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms583683(v=vs.90)) classes. [Microsoft.Ink.InkPicture](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms583740(v=vs.90)) and [Microsoft.Ink.InkEdit](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms552265(v=vs.90)) are controls that you can add to an application to collect ink. The [Microsoft.Ink.InkOverlay](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms552322(v=vs.90)) and [Microsoft.Ink.InkCollector](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms583683(v=vs.90)) can be attached to an existing window to ink-enable windows and custom controls. The WPF platform includes the control. You can add an to your application and begin collecting ink immediately. With the , the user can copy, select, and resize ink. You can add other controls to the , and the user can handwrite over those controls, too. You can create an ink-enabled custom control by adding an to it and collecting its stylus points. @@ -30,11 +30,11 @@ There are essentially three platforms that support digital ink: the Tablet PC Wi |Enable ink on a custom control|See [Creating an Ink Input Control](../../../../docs/framework/wpf/advanced/creating-an-ink-input-control.md).|See [Ink Clipboard Sample](/windows/desktop/tablet/ink-clipboard-sample).| ## Ink Data - On the Windows Forms and COM platforms, [Microsoft.Ink.InkCollector](https://msdn.microsoft.com/library/ms836493.aspx), [Microsoft.Ink.InkOverlay](https://msdn.microsoft.com/library/ms833057.aspx), [Microsoft.Ink.InkEdit](https://msdn.microsoft.com/library/ms835842.aspx), and [Microsoft.Ink.InkPicture](https://msdn.microsoft.com/library/aa514604.aspx) each expose a [Microsoft.Ink.Ink](https://msdn.microsoft.com/library/aa515768.aspx?displayProperty=nameWithType) object. The [Microsoft.Ink.Ink](https://msdn.microsoft.com/library/aa515768.aspx) object contains the data for one or more [Microsoft.Ink.Stroke](https://msdn.microsoft.com/library/ms827842.aspx?displayProperty=nameWithType) objects and exposes common methods and properties to manage and manipulate those strokes. The [Microsoft.Ink.Ink](https://msdn.microsoft.com/library/aa515768.aspx) object manages the lifetime of the strokes it contains; the [Microsoft.Ink.Ink](https://msdn.microsoft.com/library/aa515768.aspx) object creates and deletes the strokes that it owns. Each [Microsoft.Ink.Stroke](https://msdn.microsoft.com/library/ms827842.aspx) has an identifier that is unique within its parent [Microsoft.Ink.Ink](https://msdn.microsoft.com/library/aa515768.aspx) object. + On the Windows Forms and COM platforms, [Microsoft.Ink.InkCollector](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms583683(v=vs.90)), [Microsoft.Ink.InkOverlay](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms552322(v=vs.90)), [Microsoft.Ink.InkEdit](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms552265(v=vs.90)), and [Microsoft.Ink.InkPicture](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms583740(v=vs.90)) each expose a [Microsoft.Ink.Ink](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms583670(v=vs.90)) object. The [Microsoft.Ink.Ink](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms583670(v=vs.90)) object contains the data for one or more [Microsoft.Ink.Stroke](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms552692(v=vs.90)) objects and exposes common methods and properties to manage and manipulate those strokes. The [Microsoft.Ink.Ink](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms583670(v=vs.90)) object manages the lifetime of the strokes it contains; the [Microsoft.Ink.Ink](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms583670(v=vs.90)) object creates and deletes the strokes that it owns. Each [Microsoft.Ink.Stroke](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms552692(v=vs.90)) has an identifier that is unique within its parent [Microsoft.Ink.Ink](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms583670(v=vs.90)) object. - On the WPF platform, the class owns and manages its own lifetime. A group of objects can be collected together in a , which provides methods for common ink data management operations such as hit testing, erasing, transforming, and serializing the ink. A can belong to zero, one, or more objects at any give time. Instead of having a [Microsoft.Ink.Ink](https://msdn.microsoft.com/library/aa515768.aspx?displayProperty=nameWithType) object, the and contain a . + On the WPF platform, the class owns and manages its own lifetime. A group of objects can be collected together in a , which provides methods for common ink data management operations such as hit testing, erasing, transforming, and serializing the ink. A can belong to zero, one, or more objects at any give time. Instead of having a [Microsoft.Ink.Ink](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms583670(v=vs.90)) object, the and contain a . - The following pair of illustrations compares the ink data object models. On the Windows Forms and COM platforms, the [Microsoft.Ink.Ink](https://msdn.microsoft.com/library/aa515768.aspx?displayProperty=nameWithType) object constrains the lifetime of the [Microsoft.Ink.Stroke](https://msdn.microsoft.com/library/ms827842.aspx?displayProperty=nameWithType) objects, and the stylus packets belong to the individual strokes. Two or more strokes can reference the same [Microsoft.Ink.DrawingAttributes](https://msdn.microsoft.com/library/ms837931.aspx?displayProperty=nameWithType) object, as shown in the following illustration. + The following pair of illustrations compares the ink data object models. On the Windows Forms and COM platforms, the [Microsoft.Ink.Ink](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms583670(v=vs.90)) object constrains the lifetime of the [Microsoft.Ink.Stroke](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms552692(v=vs.90)) objects, and the stylus packets belong to the individual strokes. Two or more strokes can reference the same [Microsoft.Ink.DrawingAttributes](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms583636(v=vs.90)) object, as shown in the following illustration. ![Diagram of the Ink Object Model for COM/Winforms.](../../../../docs/framework/wpf/advanced/media/ink-inkownsstrokes.png "Ink_InkOwnsStrokes") @@ -46,12 +46,12 @@ There are essentially three platforms that support digital ink: the Tablet PC Wi |Task|Windows Presentation Foundation|Windows Forms and COM| |----------|-------------------------------------|---------------------------| -|Save Ink||[Microsoft.Ink.Ink.Save](https://technet.microsoft.com/library/security/microsoft.ink.ink.save(v=vs.90))| -|Load Ink|Create a with the constructor.|[Microsoft.Ink.Ink.Load](https://msdn.microsoft.com/library/microsoft.ink.ink.load(v=vs.90).aspx)| -|Hit test||[Microsoft.Ink.Ink.HitTest](https://msdn.microsoft.com/library/aa515934.aspx)| -|Copy Ink||[Microsoft.Ink.Ink.ClipboardCopy](https://msdn.microsoft.com/library/microsoft.ink.ink.clipboardcopy(v=vs.100).aspx)| -|Paste Ink||[Microsoft.Ink.Ink.ClipboardPaste](https://msdn.microsoft.com/library/microsoft.ink.ink.clipboardpaste(v=vs.100).aspx)| -|Access custom properties on a collection of strokes| (the properties are stored internally and accessed via , , and )|Use [Microsoft.Ink.Ink.ExtendedProperties](https://msdn.microsoft.com/library/microsoft.ink.ink.extendedproperties(v=vs.100).aspx)| +|Save Ink||[Microsoft.Ink.Ink.Save](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms571335(v=vs.90))| +|Load Ink|Create a with the constructor.|[Microsoft.Ink.Ink.Load](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms569609(v=vs.90))| +|Hit test||[Microsoft.Ink.Ink.HitTest](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms571330(v=vs.90))| +|Copy Ink||[Microsoft.Ink.Ink.ClipboardCopy](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms571316(v=vs.90))| +|Paste Ink||[Microsoft.Ink.Ink.ClipboardPaste](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms571318(v=vs.90))| +|Access custom properties on a collection of strokes| (the properties are stored internally and accessed via , , and )|Use [Microsoft.Ink.Ink.ExtendedProperties](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms582214(v=vs.90))| ### Sharing ink between platforms Although the platforms have different object models for the ink data, sharing the data between the platforms is very easy. The following examples save ink from a Windows Forms application and load the ink into a Windows Presentation Foundation application. @@ -78,7 +78,7 @@ There are essentially three platforms that support digital ink: the Tablet PC Wi [!code-csharp[WinFormWPFInk#LoadWinforms](../../../../samples/snippets/csharp/VS_Snippets_Wpf/WinformWPFInk/CSharp/Program.cs#loadwinforms)] [!code-vb[WinFormWPFInk#LoadWinforms](../../../../samples/snippets/visualbasic/VS_Snippets_Wpf/WinformWPFInk/VisualBasic/Module1.vb#loadwinforms)] ## Events from the Tablet Pen - The [Microsoft.Ink.InkOverlay](https://msdn.microsoft.com/library/ms833057.aspx), [Microsoft.Ink.InkCollector](https://msdn.microsoft.com/library/ms836493.aspx), and [Microsoft.Ink.InkPicture](https://msdn.microsoft.com/library/aa514604.aspx) on the Windows Forms and COM platforms receive events when the user inputs pen data. The [Microsoft.Ink.InkOverlay](https://msdn.microsoft.com/library/ms833057.aspx) or [Microsoft.Ink.InkCollector](https://msdn.microsoft.com/library/ms836493.aspx) is attached to a window or a control, and can subscribe to the events raised by the tablet input data. The thread on which these events occurs depends on whether the events are raised with a pen, a mouse, or programmatically. For more information about threading in relation to these events, see [General Threading Considerations](/windows/desktop/tablet/general-threading-considerations) and [Threads on Which an Event Can Fire](/windows/desktop/tablet/threads-on-which-an-event-can-fire). + The [Microsoft.Ink.InkOverlay](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms552322(v=vs.90)), [Microsoft.Ink.InkCollector](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms583683(v=vs.90)), and [Microsoft.Ink.InkPicture](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms583740(v=vs.90)) on the Windows Forms and COM platforms receive events when the user inputs pen data. The [Microsoft.Ink.InkOverlay](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms552322(v=vs.90)) or [Microsoft.Ink.InkCollector](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms583683(v=vs.90)) is attached to a window or a control, and can subscribe to the events raised by the tablet input data. The thread on which these events occurs depends on whether the events are raised with a pen, a mouse, or programmatically. For more information about threading in relation to these events, see [General Threading Considerations](/windows/desktop/tablet/general-threading-considerations) and [Threads on Which an Event Can Fire](/windows/desktop/tablet/threads-on-which-an-event-can-fire). On the Windows Presentation Foundation platform, the class has events for pen input. This means that every control exposes the full set of stylus events. The stylus events have tunneling/bubbling event pairs and always occur on the application thread. For more information, see [Routed Events Overview](../../../../docs/framework/wpf/advanced/routed-events-overview.md). @@ -87,9 +87,9 @@ There are essentially three platforms that support digital ink: the Tablet PC Wi ![Diagram of the Stylus events in WPF vs Winforms.](../../../../docs/framework/wpf/advanced/media/ink-stylusevents.png "Ink_StylusEvents") ## Pen Data - All three platforms provide you with ways to intercept and manipulate the data that comes in from a tablet pen. On the Windows Forms and COM Platforms, this is achieved by creating a [Microsoft.StylusInput.RealTimeStylus](https://msdn.microsoft.com/library/microsoft.stylusinput.realtimestylus(v=vs.100).aspx), attaching a window or control to it, and creating a class that implements the [Microsoft.StylusInput.IStylusSyncPlugin](https://msdn.microsoft.com/library/microsoft.stylusinput.istylussyncplugin(v=vs.100).aspx) or [Microsoft.StylusInput.IStylusAsyncPlugin](https://msdn.microsoft.com/library/microsoft.stylusinput.istylusasyncplugin(v=vs.100).aspx) interface. The custom plug-in is then added to the plug-in collection of the [Microsoft.StylusInput.RealTimeStylus](https://msdn.microsoft.com/library/microsoft.stylusinput.realtimestylus(v=vs.100).aspx). For more information about this object model, see [Architecture of the StylusInput APIs](/windows/desktop/tablet/architecture-of-the-stylusinput-apis). + All three platforms provide you with ways to intercept and manipulate the data that comes in from a tablet pen. On the Windows Forms and COM Platforms, this is achieved by creating a [Microsoft.StylusInput.RealTimeStylus](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms585724(v=vs.90)), attaching a window or control to it, and creating a class that implements the [Microsoft.StylusInput.IStylusSyncPlugin](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms575201(v=vs.90)) or [Microsoft.StylusInput.IStylusAsyncPlugin](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms575194(v=vs.90)) interface. The custom plug-in is then added to the plug-in collection of the [Microsoft.StylusInput.RealTimeStylus](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms585724(v=vs.90)). For more information about this object model, see [Architecture of the StylusInput APIs](/windows/desktop/tablet/architecture-of-the-stylusinput-apis). - On the [!INCLUDE[TLA2#tla_wpf](../../../../includes/tla2sharptla-wpf-md.md)] platform, the class exposes a collection of plug-ins, similar in design to the [Microsoft.StylusInput.RealTimeStylus](https://msdn.microsoft.com/library/microsoft.stylusinput.realtimestylus(v=vs.100).aspx). To intercept pen data, create a class that inherits from and add the object to the collection of the . For more information about this interaction, see [Intercepting Input from the Stylus](../../../../docs/framework/wpf/advanced/intercepting-input-from-the-stylus.md). + On the [!INCLUDE[TLA2#tla_wpf](../../../../includes/tla2sharptla-wpf-md.md)] platform, the class exposes a collection of plug-ins, similar in design to the [Microsoft.StylusInput.RealTimeStylus](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms585724(v=vs.90)). To intercept pen data, create a class that inherits from and add the object to the collection of the . For more information about this interaction, see [Intercepting Input from the Stylus](../../../../docs/framework/wpf/advanced/intercepting-input-from-the-stylus.md). On all platforms, a thread pool receives the ink data via stylus events and sends it to the application thread. For more information about threading on the COM and Windows Platforms, see [Threading Considerations for the StylusInput APIs](/windows/desktop/tablet/threading-considerations-for-the-stylusinput-apis). For more information about threading on the Windows Presentation Software, see [The Ink Threading Model](../../../../docs/framework/wpf/advanced/the-ink-threading-model.md). diff --git a/docs/framework/wpf/advanced/trees-in-wpf.md b/docs/framework/wpf/advanced/trees-in-wpf.md index 74e0b3df8584d..ceecaf64c7c0b 100644 --- a/docs/framework/wpf/advanced/trees-in-wpf.md +++ b/docs/framework/wpf/advanced/trees-in-wpf.md @@ -23,7 +23,7 @@ In many technologies, elements and components are organized in a tree structure ## The Logical Tree - In [!INCLUDE[TLA2#tla_winclient](../../../../includes/tla2sharptla-winclient-md.md)], you add content to UI elements by setting properties of the objects that back those elements. For example, you add items to a control by manipulating its property. By doing this, you are placing items into the that is the property value. Similarly, to add objects to a , you manipulate its property value. Here, you are adding objects to the . For a code example, see [Add an Element Dynamically](https://msdn.microsoft.com/library/d00f258a-7973-4de7-bc54-a3fc1f638419). + In [!INCLUDE[TLA2#tla_winclient](../../../../includes/tla2sharptla-winclient-md.md)], you add content to UI elements by setting properties of the objects that back those elements. For example, you add items to a control by manipulating its property. By doing this, you are placing items into the that is the property value. Similarly, to add objects to a , you manipulate its property value. Here, you are adding objects to the . For a code example, see [How to: Add an Element Dynamically](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/ms752374(v=vs.100)). In [!INCLUDE[TLA#tla_xaml](../../../../includes/tlasharptla-xaml-md.md)], when you place list items in a or controls or other UI elements in a , you also use the and properties, either explicitly or implicitly, as in the following example. diff --git a/docs/framework/wpf/advanced/troubleshooting-hybrid-applications.md b/docs/framework/wpf/advanced/troubleshooting-hybrid-applications.md index 35bea660cab91..d77d84a5347d9 100644 --- a/docs/framework/wpf/advanced/troubleshooting-hybrid-applications.md +++ b/docs/framework/wpf/advanced/troubleshooting-hybrid-applications.md @@ -111,7 +111,7 @@ ms.assetid: f440c23f-fa5d-4d5a-852f-ba61150e6405 ## See also - - -- [Interoperability in the WPF Designer](https://msdn.microsoft.com/library/2cb7c1ca-2a75-463b-8801-fba81e2b7042) +- [Interoperability in the WPF Designer](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/bb628658(v=vs.100)) - [Windows Forms and WPF Interoperability Input Architecture](../../../../docs/framework/wpf/advanced/windows-forms-and-wpf-interoperability-input-architecture.md) - [How to: Enable Visual Styles in a Hybrid Application](../../../../docs/framework/wpf/advanced/how-to-enable-visual-styles-in-a-hybrid-application.md) - [Layout Considerations for the WindowsFormsHost Element](../../../../docs/framework/wpf/advanced/layout-considerations-for-the-windowsformshost-element.md) diff --git a/docs/framework/wpf/advanced/walkthrough-binding-to-data-in-hybrid-applications.md b/docs/framework/wpf/advanced/walkthrough-binding-to-data-in-hybrid-applications.md index 17285b52ac231..08ae7b60fce54 100644 --- a/docs/framework/wpf/advanced/walkthrough-binding-to-data-in-hybrid-applications.md +++ b/docs/framework/wpf/advanced/walkthrough-binding-to-data-in-hybrid-applications.md @@ -116,7 +116,7 @@ Binding a data source to a control is essential for providing users with access 1. From the **Data** menu, select **Add New Data Source**. -2. In the **Data Source Configuration Wizard**, create a connection to the Northwind database by using a dataset. For more information, see [How to: Connect to Data in a Database](https://msdn.microsoft.com/library/6c56e54e-8834-4297-85aa-cc1a443ba556). +2. In the **Data Source Configuration Wizard**, create a connection to the Northwind database by using a dataset. For more information, see [How to: Connect to Data in a Database](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2013/fxk9yw1t(v=vs.120)). 3. When you are prompted by the **Data Source Configuration Wizard**, save the connection string as `NorthwindConnectionString`. diff --git a/docs/framework/wpf/advanced/walkthrough-creating-your-first-touch-application.md b/docs/framework/wpf/advanced/walkthrough-creating-your-first-touch-application.md index 85e2db7fe1148..2d346e0f6588d 100644 --- a/docs/framework/wpf/advanced/walkthrough-creating-your-first-touch-application.md +++ b/docs/framework/wpf/advanced/walkthrough-creating-your-first-touch-application.md @@ -27,7 +27,7 @@ ms.assetid: d69e602e-9a25-4e24-950b-e89eaa2a906b #### To create the application -1. Create a new WPF Application project in Visual Basic or Visual C# named `BasicManipulation`. For more information, see [How to: Create a New WPF Application Project](https://msdn.microsoft.com/library/1f6aea7a-33e1-4d3f-8555-1daa42e95d82). +1. Create a new WPF Application project in Visual Basic or Visual C# named `BasicManipulation`. For more information, see [How to: Create a New WPF Application Project](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/bb546958(v=vs.100)). 2. Replace the contents of MainWindow.xaml with the following XAML. diff --git a/docs/framework/wpf/advanced/walkthrough-enabling-drag-and-drop-on-a-user-control.md b/docs/framework/wpf/advanced/walkthrough-enabling-drag-and-drop-on-a-user-control.md index 76c437c7accf2..bafd567ffc1c6 100644 --- a/docs/framework/wpf/advanced/walkthrough-enabling-drag-and-drop-on-a-user-control.md +++ b/docs/framework/wpf/advanced/walkthrough-enabling-drag-and-drop-on-a-user-control.md @@ -32,7 +32,7 @@ You need Visual Studio to complete this walkthrough. ## Create the Application Project In this section, you will create the application infrastructure, which includes a main page with two panels and a . -1. Create a new WPF Application project in Visual Basic or Visual C# named `DragDropExample`. For more information, see [How to: Create a New WPF Application Project](https://msdn.microsoft.com/library/1f6aea7a-33e1-4d3f-8555-1daa42e95d82). +1. Create a new WPF Application project in Visual Basic or Visual C# named `DragDropExample`. For more information, see [How to: Create a New WPF Application Project](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/bb546958(v=vs.100)). 2. Open MainWindow.xaml. diff --git a/docs/framework/wpf/advanced/walkthrough-hosting-a-3-d-wpf-composite-control-in-windows-forms.md b/docs/framework/wpf/advanced/walkthrough-hosting-a-3-d-wpf-composite-control-in-windows-forms.md index 34c0997142779..465f90d45cc40 100644 --- a/docs/framework/wpf/advanced/walkthrough-hosting-a-3-d-wpf-composite-control-in-windows-forms.md +++ b/docs/framework/wpf/advanced/walkthrough-hosting-a-3-d-wpf-composite-control-in-windows-forms.md @@ -45,7 +45,7 @@ You need the following components to complete this walkthrough: ## Create the host project -1. Add a **WPF App (.NET Framework)** project named `WpfUserControlHost` to the solution. For more information, see [How to: Create a New WPF Application Project](https://msdn.microsoft.com/library/1f6aea7a-33e1-4d3f-8555-1daa42e95d82). +1. Add a **WPF App (.NET Framework)** project named `WpfUserControlHost` to the solution. For more information, see [How to: Create a New WPF Application Project](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/bb546958(v=vs.100)). 2. In **Solution Explorer**, add a reference to the WindowsFormsIntegration assembly, which is named WindowsFormsIntegration.dll. From e5319016bbff1bcdd10af365156f628e0cd0f8fa Mon Sep 17 00:00:00 2001 From: Maira Wenzel Date: Fri, 22 Feb 2019 12:22:01 -0800 Subject: [PATCH 4/5] Apply suggestions from code review Accepting Maira's suggestions for XPSDrv and another change. Still need to fix *How to: Create a New WPF Application Project* manually. Co-Authored-By: DennisLee-DennisLee --- docs/framework/wpf/advanced/printing-overview.md | 4 ++-- .../the-ink-object-model-windows-forms-and-com-versus-wpf.md | 3 ++- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/framework/wpf/advanced/printing-overview.md b/docs/framework/wpf/advanced/printing-overview.md index 9977198f65561..96fdd8062948b 100644 --- a/docs/framework/wpf/advanced/printing-overview.md +++ b/docs/framework/wpf/advanced/printing-overview.md @@ -51,7 +51,7 @@ With Microsoft .NET Framework, application developers using Windows Presentation - Print Schema. The public schema is updated regularly and enables rapid extension of device capabilities. (See **PrintTicket and PrintCapabilities** below.) -- Extensible Filter Pipeline. The [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] printer driver (XPSDrv) filter pipeline was designed to enable both direct and scalable printing of [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] documents. (Look up "XPSDrv" in the [Windows Driver Kit documentation](/windows-hardware/drivers/).) +- Extensible Filter Pipeline. The [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] printer driver (XPSDrv) filter pipeline was designed to enable both direct and scalable printing of [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] documents. For more information, see [XPSDrv Printer Drivers](/windows-hardware/drivers/print/xpsdrv-printer-drivers). ### Print Path Architecture While both [!INCLUDE[TLA2#tla_win32](../../../../includes/tla2sharptla-win32-md.md)] and .NET Framework applications support [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)], [!INCLUDE[TLA2#tla_win32](../../../../includes/tla2sharptla-win32-md.md)] and Windows Forms applications use a [!INCLUDE[TLA2#tla_gdi](../../../../includes/tla2sharptla-gdi-md.md)] to [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] conversion in order to create [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] formatted content for the [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] printer driver (XPSDrv). These applications are not required to use the [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] print path, and can continue to use [!INCLUDE[TLA#tla_emf](../../../../includes/tlasharptla-emf-md.md)] based printing. However, most [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] features and enhancements are only available to applications that target the [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] print path. @@ -104,7 +104,7 @@ With Microsoft .NET Framework, application developers using Windows Presentation For applications that do not require [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] functionality or support, the current [!INCLUDE[TLA2#tla_gdi](../../../../includes/tla2sharptla-gdi-md.md)] print path remains unchanged. -- For additional reference material on the [!INCLUDE[TLA2#tla_gdi](../../../../includes/tla2sharptla-gdi-md.md)] print path and the various [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] conversion options, see [Microsoft XPS Document Converter (MXDC)](/windows/desktop/printdocs/microsoft-xps-document-converter--mxdc-) and "XPSDrv" in the [Windows Driver Kit documentation](/windows-hardware/drivers/). +- For additional reference material on the [!INCLUDE[TLA2#tla_gdi](../../../../includes/tla2sharptla-gdi-md.md)] print path and the various [!INCLUDE[TLA2#tla_metro](../../../../includes/tla2sharptla-metro-md.md)] conversion options, see [Microsoft XPS Document Converter (MXDC)](/windows/desktop/printdocs/microsoft-xps-document-converter--mxdc-) and [XPSDrv Printer Drivers](/windows-hardware/drivers/print/xpsdrv-printer-drivers). ## XPSDrv Driver Model diff --git a/docs/framework/wpf/advanced/the-ink-object-model-windows-forms-and-com-versus-wpf.md b/docs/framework/wpf/advanced/the-ink-object-model-windows-forms-and-com-versus-wpf.md index dc5bbb6c7145b..57ebda056c3ca 100644 --- a/docs/framework/wpf/advanced/the-ink-object-model-windows-forms-and-com-versus-wpf.md +++ b/docs/framework/wpf/advanced/the-ink-object-model-windows-forms-and-com-versus-wpf.md @@ -78,7 +78,8 @@ There are essentially three platforms that support digital ink: the Tablet PC Wi [!code-csharp[WinFormWPFInk#LoadWinforms](../../../../samples/snippets/csharp/VS_Snippets_Wpf/WinformWPFInk/CSharp/Program.cs#loadwinforms)] [!code-vb[WinFormWPFInk#LoadWinforms](../../../../samples/snippets/visualbasic/VS_Snippets_Wpf/WinformWPFInk/VisualBasic/Module1.vb#loadwinforms)] ## Events from the Tablet Pen - The [Microsoft.Ink.InkOverlay](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms552322(v=vs.90)), [Microsoft.Ink.InkCollector](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms583683(v=vs.90)), and [Microsoft.Ink.InkPicture](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms583740(v=vs.90)) on the Windows Forms and COM platforms receive events when the user inputs pen data. The [Microsoft.Ink.InkOverlay](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms552322(v=vs.90)) or [Microsoft.Ink.InkCollector](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms583683(v=vs.90)) is attached to a window or a control, and can subscribe to the events raised by the tablet input data. The thread on which these events occurs depends on whether the events are raised with a pen, a mouse, or programmatically. For more information about threading in relation to these events, see [General Threading Considerations](/windows/desktop/tablet/general-threading-considerations) and [Threads on Which an Event Can Fire](/windows/desktop/tablet/threads-on-which-an-event-can-fire). + + The [Microsoft.Ink.InkOverlay](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms552322(v=vs.90)), [Microsoft.Ink.InkCollector](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms583683(v=vs.90)), and [Microsoft.Ink.InkPicture](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms583740(v=vs.90)) on the Windows Forms and COM platforms receive events when the user inputs pen data. The [Microsoft.Ink.InkOverlay](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms552322(v=vs.90)) or [Microsoft.Ink.InkCollector](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms583683(v=vs.90)) is attached to a window or a control, and can subscribe to the events raised by the tablet input data. The thread on which these events occurs depends on whether the events are raised with a pen, a mouse, or programmatically. For more information about threading in relation to these events, see [General Threading Considerations](/windows/desktop/tablet/general-threading-considerations) and [Threads on Which an Event Can Fire](/windows/desktop/tablet/threads-on-which-an-event-can-fire). On the Windows Presentation Foundation platform, the class has events for pen input. This means that every control exposes the full set of stylus events. The stylus events have tunneling/bubbling event pairs and always occur on the application thread. For more information, see [Routed Events Overview](../../../../docs/framework/wpf/advanced/routed-events-overview.md). From 6e34aa786653ce32270da5e7cf1cf0def007daa6 Mon Sep 17 00:00:00 2001 From: Dennis Lee Date: Fri, 22 Feb 2019 12:32:20 -0800 Subject: [PATCH 5/5] Correcting 3 [How to: Create a New WPF Application Project] links. --- .../walkthrough-creating-your-first-touch-application.md | 2 +- .../walkthrough-enabling-drag-and-drop-on-a-user-control.md | 2 +- ...ough-hosting-a-3-d-wpf-composite-control-in-windows-forms.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/framework/wpf/advanced/walkthrough-creating-your-first-touch-application.md b/docs/framework/wpf/advanced/walkthrough-creating-your-first-touch-application.md index 2d346e0f6588d..80286bb6fbcd4 100644 --- a/docs/framework/wpf/advanced/walkthrough-creating-your-first-touch-application.md +++ b/docs/framework/wpf/advanced/walkthrough-creating-your-first-touch-application.md @@ -27,7 +27,7 @@ ms.assetid: d69e602e-9a25-4e24-950b-e89eaa2a906b #### To create the application -1. Create a new WPF Application project in Visual Basic or Visual C# named `BasicManipulation`. For more information, see [How to: Create a New WPF Application Project](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/bb546958(v=vs.100)). +1. Create a new WPF Application project in Visual Basic or Visual C# named `BasicManipulation`. For more information, see [Walkthrough: My first WPF desktop application](../getting-started/walkthrough-my-first-wpf-desktop-application.md). 2. Replace the contents of MainWindow.xaml with the following XAML. diff --git a/docs/framework/wpf/advanced/walkthrough-enabling-drag-and-drop-on-a-user-control.md b/docs/framework/wpf/advanced/walkthrough-enabling-drag-and-drop-on-a-user-control.md index bafd567ffc1c6..da9ca83683b0a 100644 --- a/docs/framework/wpf/advanced/walkthrough-enabling-drag-and-drop-on-a-user-control.md +++ b/docs/framework/wpf/advanced/walkthrough-enabling-drag-and-drop-on-a-user-control.md @@ -32,7 +32,7 @@ You need Visual Studio to complete this walkthrough. ## Create the Application Project In this section, you will create the application infrastructure, which includes a main page with two panels and a . -1. Create a new WPF Application project in Visual Basic or Visual C# named `DragDropExample`. For more information, see [How to: Create a New WPF Application Project](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/bb546958(v=vs.100)). +1. Create a new WPF Application project in Visual Basic or Visual C# named `DragDropExample`. For more information, see [Walkthrough: My first WPF desktop application](../getting-started/walkthrough-my-first-wpf-desktop-application.md). 2. Open MainWindow.xaml. diff --git a/docs/framework/wpf/advanced/walkthrough-hosting-a-3-d-wpf-composite-control-in-windows-forms.md b/docs/framework/wpf/advanced/walkthrough-hosting-a-3-d-wpf-composite-control-in-windows-forms.md index 465f90d45cc40..d7e4736f9caf7 100644 --- a/docs/framework/wpf/advanced/walkthrough-hosting-a-3-d-wpf-composite-control-in-windows-forms.md +++ b/docs/framework/wpf/advanced/walkthrough-hosting-a-3-d-wpf-composite-control-in-windows-forms.md @@ -45,7 +45,7 @@ You need the following components to complete this walkthrough: ## Create the host project -1. Add a **WPF App (.NET Framework)** project named `WpfUserControlHost` to the solution. For more information, see [How to: Create a New WPF Application Project](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/bb546958(v=vs.100)). +1. Add a **WPF App (.NET Framework)** project named `WpfUserControlHost` to the solution. For more information, see [Walkthrough: My first WPF desktop application](../getting-started/walkthrough-my-first-wpf-desktop-application.md). 2. In **Solution Explorer**, add a reference to the WindowsFormsIntegration assembly, which is named WindowsFormsIntegration.dll.