update links in framework/xaml-services folder (#15642)

gewarren · web-flow · commit 9fb43bb93f82 · 2019-11-01T14:13:13.000-07:00
diff --git a/docs/framework/xaml-services/index.md b/docs/framework/xaml-services/index.md
@@ -27,7 +27,7 @@ This topic describes the capabilities of a technology set known as .NET Framewor
   
 - Using the `Lookup` or `Invoker` techniques to influence the XAML type system and how type backings are evaluated.  
   
- If you are looking for introductory material on XAML as a language, you might try [XAML Overview (WPF)](../wpf/advanced/xaml-overview-wpf.md). That topic discusses XAML for an audience that is new both to [!INCLUDE[TLA#tla_winclient](../../../includes/tlasharptla-winclient-md.md)] and also to using XAML markup and XAML language features. Another useful document is the introductory material in the [XAML language specification](https://go.microsoft.com/fwlink/?LinkId=114525).  
+ If you are looking for introductory material on XAML as a language, you might try [XAML Overview (WPF)](../../desktop-wpf/fundamentals/xaml.md). That topic discusses XAML for an audience that is new both to [!INCLUDE[TLA#tla_winclient](../../../includes/tlasharptla-winclient-md.md)] and also to using XAML markup and XAML language features. Another useful document is the introductory material in the [XAML language specification](https://go.microsoft.com/fwlink/?LinkId=114525).  
   
 ## .NET Framework XAML Services and System.Xaml in the .NET Architecture  
  In previous versions of Microsoft .NET Framework, support for XAML language features was implemented by frameworks that built on Microsoft .NET Framework ([!INCLUDE[TLA#tla_winclient](../../../includes/tlasharptla-winclient-md.md)], Windows Workflow Foundation and Windows Communication Foundation (WCF)), and therefore varied in its behavior and the API used depending on which specific framework you were using. This included the XAML parser and its object graph creation mechanism, XAML language intrinsics, serialization support, and so on.  
diff --git a/docs/framework/xaml-services/type-converters-for-xaml-overview.md b/docs/framework/xaml-services/type-converters-for-xaml-overview.md
@@ -105,4 +105,4 @@ Type converters supply logic for an object writer that converts from a string in
 
 - <xref:System.ComponentModel.TypeConverterAttribute>
 - [Type Converters and Markup Extensions for XAML](type-converters-and-markup-extensions-for-xaml.md)
-- [XAML Overview (WPF)](../wpf/advanced/xaml-overview-wpf.md)
+- [XAML Overview (WPF)](../../desktop-wpf/fundamentals/xaml.md)
diff --git a/docs/framework/xaml-services/whitespace-processing-in-xaml.md b/docs/framework/xaml-services/whitespace-processing-in-xaml.md
@@ -70,6 +70,6 @@ The language rules for XAML state that significant white space must be processed
   
 ## See also
 
-- [XAML overview (WPF)](../wpf/advanced/xaml-overview-wpf.md)
+- [XAML overview (WPF)](../../desktop-wpf/fundamentals/xaml.md)
 - [XML character entities and XAML](xml-character-entities-and-xaml.md)
 - [xml:space handling in XAML](xml-space-handling-in-xaml.md)
diff --git a/docs/framework/xaml-services/x-arguments-directive.md b/docs/framework/xaml-services/x-arguments-directive.md
@@ -103,4 +103,4 @@ public Food TryLookupFood(string name)
 ## See also
 
 - [Defining Custom Types for Use with .NET Framework XAML Services](defining-custom-types-for-use-with-net-framework-xaml-services.md)
-- [XAML Overview (WPF)](../wpf/advanced/xaml-overview-wpf.md)
+- [XAML Overview (WPF)](../../desktop-wpf/fundamentals/xaml.md)
diff --git a/docs/framework/xaml-services/x-code-intrinsic-xaml-type.md b/docs/framework/xaml-services/x-code-intrinsic-xaml-type.md
@@ -46,4 +46,4 @@ Allows placement of code within a XAML production. Such code can either be compi
 
 - [x:Class Directive](x-class-directive.md)
 - [Code-Behind and XAML in WPF](../wpf/advanced/code-behind-and-xaml-in-wpf.md)
-- [XAML Overview (WPF)](../wpf/advanced/xaml-overview-wpf.md)
+- [XAML Overview (WPF)](../../desktop-wpf/fundamentals/xaml.md)
diff --git a/docs/framework/xaml-services/x-key-directive.md b/docs/framework/xaml-services/x-key-directive.md
@@ -42,7 +42,7 @@ Uniquely identifies elements that are created and referenced in a XAML-defined d
 |`markupExtensionUsage`|Within the markup extension delimiters {}, a markup extension usage that provides an object to use as a key. See Remarks.|  
   
 ## Remarks  
- `x:Key` supports the XAML resource dictionary concept. XAML as a language doesn't define a resource dictionary implementation, that is left to specific UI frameworks. To learn more about how XAML resource dictionaries are implemented in WPF, see [XAML Resources](../wpf/advanced/xaml-resources.md).  
+ `x:Key` supports the XAML resource dictionary concept. XAML as a language doesn't define a resource dictionary implementation, that is left to specific UI frameworks. To learn more about how XAML resource dictionaries are implemented in WPF, see [XAML Resources](../../desktop-wpf/fundamentals/xaml-resources-define.md).  
   
  In XAML 2006 and WPF, `x:Key` must be provided as an attribute. You can still use nonstring keys, but this requires a markup extension usage in order to provide the nonstring value in attribute form. If you are using XAML 2009, `x:Key` can be specified as an element, to explicitly support dictionaries keyed by object types other than strings without requiring a markup extension intermediate. See the "XAML 2009" section in this topic. The remainder of the Remarks section applies specifically to the XAML 2006 implementation.  
   
@@ -106,6 +106,6 @@ keyObject
   
 ## See also
 
-- [XAML Resources](../wpf/advanced/xaml-resources.md)
+- [XAML Resources](../../desktop-wpf/fundamentals/xaml-resources-define.md)
 - [Resources and Code](../wpf/advanced/resources-and-code.md)
 - [StaticResource Markup Extension](../wpf/advanced/staticresource-markup-extension.md)
diff --git a/docs/framework/xaml-services/x-name-directive.md b/docs/framework/xaml-services/x-name-directive.md
@@ -44,7 +44,7 @@ Uniquely identifies XAML-defined elements in a XAML namescope. XAML namescopes a
   
  For a WPF application that uses the Microsoft Visual Basic targets and includes XAML files with `Page` build action, a separate reference property is created during compilation that adds the `WithEvents` keyword to all elements that have an `x:Name`, to support `Handles` syntax for event handler delegates. This property is always public. For more information, see [Visual Basic and WPF Event Handling](../wpf/advanced/visual-basic-and-wpf-event-handling.md).  
   
- `x:Name` is used by the WPF XAML processor to register a name into a XAML namescope at load time, even for cases where the page is not markup-compiled by build actions (for example, loose XAML of a resource dictionary). One reason for this behavior is because the `x:Name` is potentially needed for <xref:System.Windows.Data.Binding.ElementName%2A> binding. For details, see [Data Binding Overview](../wpf/data/data-binding-overview.md).  
+ `x:Name` is used by the WPF XAML processor to register a name into a XAML namescope at load time, even for cases where the page is not markup-compiled by build actions (for example, loose XAML of a resource dictionary). One reason for this behavior is because the `x:Name` is potentially needed for <xref:System.Windows.Data.Binding.ElementName%2A> binding. For details, see [Data Binding Overview](../../desktop-wpf/data/data-binding-overview.md).  
   
  As mentioned previously, `x:Name` (or `Name`) should not be applied in situations that also use `x:Key`. The [!INCLUDE[TLA2#tla_winclient](../../../includes/tla2sharptla-winclient-md.md)] <xref:System.Windows.ResourceDictionary> has a special behavior of defining itself as a XAML namescope but returning Not Implemented or null values for <xref:System.Windows.Markup.INameScope> APIs as a way to enforce this behavior. If the WPF XAML parser encounters `Name` or `x:Name` in a XAML-defined <xref:System.Windows.ResourceDictionary>, the name is not added to any XAML namescope. Attempting to find that name from any XAML namescope and the `FindName` methods will not return valid results.  
   
diff --git a/docs/framework/xaml-services/x-null-markup-extension.md b/docs/framework/xaml-services/x-null-markup-extension.md
@@ -41,5 +41,5 @@ Specifies `null` as a value for a XAML member.
 ## See also
 
 - <xref:System.Windows.DependencyProperty.UnsetValue>
-- [XAML Overview (WPF)](../wpf/advanced/xaml-overview-wpf.md)
+- [XAML Overview (WPF)](../../desktop-wpf/fundamentals/xaml.md)
 - [Markup Extensions and WPF XAML](../wpf/advanced/markup-extensions-and-wpf-xaml.md)
diff --git a/docs/framework/xaml-services/x-shared-attribute.md b/docs/framework/xaml-services/x-shared-attribute.md
@@ -27,7 +27,7 @@ When set to `false`, modifies WPF resource-retrieval behavior so that requests f
   
  Modifying an object that is returned through a resource API, such as <xref:System.Windows.FrameworkElement.FindResource%2A>, or modifying an object directly within a <xref:System.Windows.ResourceDictionary>, changes the original resource. If references to that resource were dynamic resource references, the consumers of that resource get the changed resource.  
   
- If references to the resource were static resource references, changes to the resource after [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] processing time are irrelevant. For more information about static versus dynamic resource references, see [XAML Resources](../wpf/advanced/xaml-resources.md).  
+ If references to the resource were static resource references, changes to the resource after [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] processing time are irrelevant. For more information about static versus dynamic resource references, see [XAML Resources](../../desktop-wpf/fundamentals/xaml-resources-define.md).  
   
  Explicitly specifying `x:Shared="true"` is rarely done, because that is already the default. There is no direct code equivalent for `x:Shared` in the WPF object model; it can only be specified in a XAML usage and must be processed either by the default WPF behavior or in an intermediate XAML node stream on the load path if processed using .NET Framework XAML Services and its XAML readers.  
   
@@ -46,5 +46,5 @@ When set to `false`, modifies WPF resource-retrieval behavior so that requests f
 ## See also
 
 - <xref:System.Windows.ResourceDictionary>
-- [XAML Resources](../wpf/advanced/xaml-resources.md)
+- [XAML Resources](../../desktop-wpf/fundamentals/xaml-resources-define.md)
 - [Base Elements](../wpf/advanced/base-elements.md)
diff --git a/docs/framework/xaml-services/x-type-markup-extension.md b/docs/framework/xaml-services/x-type-markup-extension.md
@@ -77,5 +77,5 @@ Supplies the CLR <xref:System.Type> object that is the underlying type for a spe
 
 - <xref:System.Windows.Style>
 - [Styling and Templating](../wpf/controls/styling-and-templating.md)
-- [XAML Overview (WPF)](../wpf/advanced/xaml-overview-wpf.md)
+- [XAML Overview (WPF)](../../desktop-wpf/fundamentals/xaml.md)
 - [Markup Extensions and WPF XAML](../wpf/advanced/markup-extensions-and-wpf-xaml.md)
diff --git a/docs/framework/xaml-services/x-xdata-intrinsic-xaml-type.md b/docs/framework/xaml-services/x-xdata-intrinsic-xaml-type.md
@@ -39,12 +39,12 @@ Enables placement of XML data islands within a XAML production. XML elements wit
 ## WPF Usage Notes  
  The `x:XData` object is primarily used as a child object of an <xref:System.Windows.Data.XmlDataProvider>, or alternatively, as the child object of the <xref:System.Windows.Data.XmlDataProvider.XmlSerializer%2A?displayProperty=nameWithType> property (in XAML, this is typically expressed in property element syntax).  
   
- The data should typically redefine the base XML namespace within the data island to be a new default XML namespace (set to an empty string). This is easiest for simple data islands because the <xref:System.Windows.Data.Binding.XPath%2A> expressions that are used to reference and bind to the data can avoid inclusion of prefixes. More complex data islands might define multiple prefixes for the data and use a specific prefix for the XML namespace at the root. In this case, all <xref:System.Windows.Data.Binding.XPath%2A> expression references should include the appropriate namespace-mapped prefix. For more information, see [Data Binding Overview](../wpf/data/data-binding-overview.md).  
+ The data should typically redefine the base XML namespace within the data island to be a new default XML namespace (set to an empty string). This is easiest for simple data islands because the <xref:System.Windows.Data.Binding.XPath%2A> expressions that are used to reference and bind to the data can avoid inclusion of prefixes. More complex data islands might define multiple prefixes for the data and use a specific prefix for the XML namespace at the root. In this case, all <xref:System.Windows.Data.Binding.XPath%2A> expression references should include the appropriate namespace-mapped prefix. For more information, see [Data Binding Overview](../../desktop-wpf/data/data-binding-overview.md).  
   
  Technically, `x:XData` can be used as the content of any property of type <xref:System.Xml.Serialization.IXmlSerializable>. However, <xref:System.Windows.Data.XmlDataProvider.XmlSerializer%2A?displayProperty=nameWithType> is the only prominent implementation.  
   
 ## See also
 
 - <xref:System.Windows.Data.XmlDataProvider>
-- [Data Binding Overview](../wpf/data/data-binding-overview.md)
+- [Data Binding Overview](../../desktop-wpf/data/data-binding-overview.md)
 - [Binding Markup Extension](../wpf/advanced/binding-markup-extension.md)
diff --git a/docs/framework/xaml-services/xaml-2009-language-features.md b/docs/framework/xaml-services/xaml-2009-language-features.md
@@ -28,4 +28,4 @@ XAML 2009 is the shorthand term for new XAML language features that extend the e
   
 ## See also
 
-- [XAML Overview (WPF)](../wpf/advanced/xaml-overview-wpf.md)
+- [XAML Overview (WPF)](../../desktop-wpf/fundamentals/xaml.md)
diff --git a/docs/framework/xaml-services/xamlname-grammar.md b/docs/framework/xaml-services/xamlname-grammar.md
@@ -40,7 +40,7 @@ CombiningCharacter ::= UnicodeMn | UnicodeMc
 | Nd                 | Number, Decimal               |
 | Nl                 | Number, Letter                |
  
- XAML defines a second grammar, DottedXamlName, that is used for property and event qualified references, and also for attached members. For more information, see <xref:System.Windows.DependencyProperty> and [XAML Overview (WPF)](../wpf/advanced/xaml-overview-wpf.md).  
+ XAML defines a second grammar, DottedXamlName, that is used for property and event qualified references, and also for attached members. For more information, see <xref:System.Windows.DependencyProperty> and [XAML Overview (WPF)](../../desktop-wpf/fundamentals/xaml.md).  
   
  String values that are of type DottedXamlName must conform to the following grammar:  
   
diff --git a/docs/framework/xaml-services/xml-character-entities-and-xaml.md b/docs/framework/xaml-services/xml-character-entities-and-xaml.md
@@ -58,7 +58,7 @@ XAML uses character entities defined in XML for special characters. This topic d
   
 ## See also
 
-- [XAML Overview (WPF)](../wpf/advanced/xaml-overview-wpf.md)
+- [XAML Overview (WPF)](../../desktop-wpf/fundamentals/xaml.md)
 - [Markup Extensions and WPF XAML](../wpf/advanced/markup-extensions-and-wpf-xaml.md)
 - [XamlName Grammar](xamlname-grammar.md)
 - [White-space processing in XAML](whitespace-processing-in-xaml.md)
diff --git a/docs/framework/xaml-services/xml-space-handling-in-xaml.md b/docs/framework/xaml-services/xml-space-handling-in-xaml.md
@@ -37,4 +37,4 @@ The `xml:space` attribute is an XML-defined attribute that declares the signific
 ## See also
 
 - [White-space processing in XAML](whitespace-processing-in-xaml.md)
-- [XAML Overview (WPF)](../wpf/advanced/xaml-overview-wpf.md)
+- [XAML Overview (WPF)](../../desktop-wpf/fundamentals/xaml.md)
