mirror of
https://github.com/Stone-Red-Code/docs-desktop.git
synced 2026-09-07 23:43:19 +02:00
WPF publish initial content (#1032)
* Add overview article for new WPF (#178) * Remove previous WPF .NET 5 content * Overview article * New article: Create new WPF project (#183) * Basic index file * Finish article for new project. * acro * markdown fix * Fix build errors * fix code lang * fix code lang * Add differences article for WPF (#186) * Fix VS version for create app * Add differences article * Minor * fix overview styles code * Add code langs for overview * Port Window Overview WPF article (#1011) * Add Window overview article * Add TOC * Remove temp code * Fix headers * Port final Windows related articles (#1015) * Initial test commit * Add system dialogs * 75% complete * Add images * Fix linter * Add to toc * Add more howto * Fix code * Add get/set main window * Add missing code * Add to toc * Fix warnings * Fix warnings * missing code * Update see also * fix xref * Migrate wpf net core controls-styles articles (#1023) * Migrate control-styles * Fix links * Fix links * Port databinding article. (#1022) * Migrated databinding overview * update toc * Fix links/snippets * fix links * Move to correct folder * Port initial resources docs (#1026) * initial resources docs * Build errors * Update dotnet-desktop-guide/net/wpf/systems/xaml-resources-overview.md Co-authored-by: Genevieve Warren <[email protected]> * Apply suggestions from code review Co-authored-by: Genevieve Warren <[email protected]> * Feedback * Add app article * Add system article * Minor * meta * fix toc * Apply suggestions from code review Co-authored-by: Genevieve Warren <[email protected]> Co-authored-by: Genevieve Warren <[email protected]> * Add xaml article * reformat redirect * Redirects * WPF update XAML article (#1031) * convert snippets * minor edits * minor * Fix warnings * Fixes #1028 * Fixes #1028 * Apply suggestions from code review Co-authored-by: Genevieve Warren <[email protected]> * update redirects Co-authored-by: Genevieve Warren <[email protected]> * minor updates to link * Readd migration article * Warning fixes * Fix lint * Minor updates * Fix warnings for TOC/YML * last warnings Co-authored-by: Genevieve Warren <[email protected]>
This commit is contained in:
Andy (Steve) De George
co-authored by
Genevieve Warren
Genevieve Warren
parent
a3b012ae99
commit
ea8529f082
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: "XAML Services"
|
||||
description: "Describes the capabilities of a .NET XAML Services. Services include readers and writers, schema classes and schema support factories, attributing of classes, XAML language support, and other XAML language features."
|
||||
ms.date: "03/30/2017"
|
||||
helpviewer_keywords:
|
||||
- "XAML [XAML Services], System.Xaml concepts"
|
||||
@@ -29,7 +30,7 @@ Conceptual documentation for .NET XAML Services assumes that you have previous e
|
||||
|
||||
- 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)](../net/wpf/fundamentals/xaml.md). That topic discusses XAML for an audience that is new both to Windows Presentation Foundation (WPF) and also to using XAML markup and XAML language features. Another useful document is the introductory material in the [XAML language specification](/previous-versions/msp-n-p/ff650760(v=pandp.10)).
|
||||
If you are looking for introductory material on XAML as a language, you might try [XAML overview (WPF .NET)](../net/wpf/xaml/index.md). That topic discusses XAML for an audience that is new both to Windows Presentation Foundation (WPF) and also to using XAML markup and XAML language features. Another useful document is the introductory material in the [XAML language specification](/previous-versions/msp-n-p/ff650760(v=pandp.10)).
|
||||
|
||||
## .NET XAML Services and `System.Xaml` in the .NET Architecture
|
||||
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: "Type Converters for XAML Overview"
|
||||
description: "Type converters provide logic for an object writer that converts a string value in XAML markup into particular objects in an object graph."
|
||||
ms.date: "03/30/2017"
|
||||
helpviewer_keywords:
|
||||
- "XAML [XAML Services], type converters"
|
||||
@@ -115,4 +116,4 @@ If you are working with a XAML node stream, the action or end result of a type c
|
||||
|
||||
- <xref:System.ComponentModel.TypeConverterAttribute>
|
||||
- [Type Converters and Markup Extensions for XAML](type-converters-and-markup-extensions.md)
|
||||
- [XAML Overview (WPF)](../net/wpf/fundamentals/xaml.md)
|
||||
- [XAML overview (WPF .NET)](../net/wpf/xaml/index.md)
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: "White-space processing in XAML"
|
||||
description: "This article describes the XAML language rules regarding how white space is handled."
|
||||
ms.date: "03/30/2017"
|
||||
helpviewer_keywords:
|
||||
- "East Asian characters [XAML Services]"
|
||||
@@ -72,6 +73,6 @@ Also, certain inline elements that connote a line break in a flow document model
|
||||
|
||||
## See also
|
||||
|
||||
- [XAML overview (WPF)](../net/wpf/fundamentals/xaml.md)
|
||||
- [XAML overview (WPF .NET)](../net/wpf/xaml/index.md)
|
||||
- [XML character entities and XAML](xml-character-entities.md)
|
||||
- [xml:space handling in XAML](xml-space-handling.md)
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: "XAML 2009 Language Features"
|
||||
description: "Describes the language features specific to the XAML 2009 specification."
|
||||
ms.date: "03/30/2017"
|
||||
helpviewer_keywords:
|
||||
- "XAML 2009 [XAML Services]"
|
||||
@@ -31,4 +32,4 @@ For attributes that are backed by events, XAML 2006 presumes that markup compila
|
||||
|
||||
## See also
|
||||
|
||||
- [XAML Overview (WPF)](../net/wpf/fundamentals/xaml.md)
|
||||
- [XAML overview (WPF .NET)](../net/wpf/xaml/index.md)
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: "XamlName Grammar"
|
||||
description: "Describes what the XAML language specification related to XamlName Grammer."
|
||||
ms.date: "03/30/2017"
|
||||
helpviewer_keywords:
|
||||
- "DottedXamlName grammar [XAML Services]"
|
||||
@@ -42,7 +43,7 @@ Which assumes the following general category values as defined in the Unicode Ch
|
||||
| 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)](../net/wpf/fundamentals/xaml.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 .NET)](../net/wpf/xaml/index.md).
|
||||
|
||||
String values that are of type DottedXamlName must conform to the following grammar:
|
||||
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: "x:Arguments Directive"
|
||||
description: "The x:Arguments directive packages construction arguments for non-parameterless constructor object elements in XAML."
|
||||
ms.date: "03/30/2017"
|
||||
helpviewer_keywords:
|
||||
- "x:Arguments directive [XAML Services]"
|
||||
@@ -33,7 +34,7 @@ Packages construction arguments for a non-parameterless constructor object eleme
|
||||
|
||||
## XAML Values
|
||||
|
||||
|||
|
||||
| Value | Description |
|
||||
|-|-|
|
||||
|`oneOrMoreObjectElements`|One or more object elements that specify arguments to be passed to the backing non-parameterless constructor or factory method.<br /><br /> Typical usage is to use initialization text within the object elements to specify the actual argument values. See Examples section.<br /><br /> The order of the elements is significant. The XAML types in order must match the types and type order of the backing constructor or factory method overload.|
|
||||
|`methodName`|The name of the factory method that should process any `x:Arguments` arguments.|
|
||||
@@ -107,4 +108,4 @@ switch (name) {
|
||||
## See also
|
||||
|
||||
- [Defining Custom Types for Use with .NET XAML Services](define-custom-types.md)
|
||||
- [XAML Overview (WPF)](../net/wpf/fundamentals/xaml.md)
|
||||
- [XAML overview (WPF .NET)](../net/wpf/xaml/index.md)
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: "x:Code Intrinsic XAML Type"
|
||||
description: "Describes how the x:Code XML type allows code to be compiled by the XAML processor."
|
||||
ms.date: "03/30/2017"
|
||||
f1_keywords:
|
||||
- "Code"
|
||||
@@ -48,4 +49,4 @@ Code declared within `x:Code` for WPF has several notable limitations:
|
||||
|
||||
- [x:Class Directive](xclass-directive.md)
|
||||
- [Code-Behind and XAML in WPF](../framework/wpf/advanced/code-behind-and-xaml-in-wpf.md)
|
||||
- [XAML Overview (WPF)](../net/wpf/fundamentals/xaml.md)
|
||||
- [XAML overview (WPF .NET)](../net/wpf/xaml/index.md)
|
||||
|
||||
@@ -1,6 +1,7 @@
|
||||
---
|
||||
title: "x:Key Directive"
|
||||
ms.date: "03/30/2017"
|
||||
description: "The x:Key directive identifies elements that are created and referenced in a XAML-defined dictionary."
|
||||
f1_keywords:
|
||||
- "xKey"
|
||||
- "Key"
|
||||
@@ -37,14 +38,14 @@ Uniquely identifies elements that are created and referenced in a XAML-defined d
|
||||
|
||||
## XAML Values
|
||||
|
||||
|||
|
||||
| Value | Description |
|
||||
|-|-|
|
||||
|`stringKeyValue`|A text string to use as a key. The text string must conform to the [XamlName Grammar](xamlname-grammar.md).|
|
||||
|`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](../net/wpf/fundamentals/xaml-resources-define.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 [Overview of XAML resources (WPF .NET)](../net/wpf/systems/xaml-resources-overview.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.
|
||||
|
||||
@@ -60,7 +61,7 @@ Uniquely identifies elements that are created and referenced in a XAML-defined d
|
||||
|
||||
- Some WPF types declare an implicit key for dictionary usage. For example, a <xref:System.Windows.Style> with a <xref:System.Windows.Style.TargetType%2A>, or a <xref:System.Windows.DataTemplate> with a <xref:System.Windows.DataTemplate.DataType%2A>, can be in a <xref:System.Windows.ResourceDictionary> and use the implicit key.
|
||||
|
||||
- WPF supports a merged resource dictionary concept. Keys can be shared between the merged dictionaries, and the shared key behavior can be accessed using <xref:System.Windows.FrameworkContentElement.FindResource%2A>. For more information, see [Merged Resource Dictionaries](../framework/wpf/advanced/merged-resource-dictionaries.md).
|
||||
- WPF supports a merged resource dictionary concept. Keys can be shared between the merged dictionaries, and the shared key behavior can be accessed using <xref:System.Windows.FrameworkContentElement.FindResource%2A>. For more information, see [Merged resource dictionaries](../net/wpf/systems/xaml-resources-merged-dictionaries.md).
|
||||
|
||||
In the overall WPF XAML implementation and application model, key uniqueness is not checked by the XAML markup compiler. Instead, missing or nonunique `x:Key` values cause load-time XAML parser errors. However, Visual Studio handling of dictionaries for WPF can often note such errors in the design phase.
|
||||
|
||||
@@ -72,7 +73,7 @@ Uniquely identifies elements that are created and referenced in a XAML-defined d
|
||||
|
||||
As stated previously, the value of a key can be supplied through a markup extension and can be other than a string value. An example WPF scenario is that the value of `x:Key` may be a [ComponentResourceKey](../framework/wpf/advanced/componentresourcekey-markup-extension.md). Certain controls expose a style key of that type for a custom style resource that influences part of the appearance and behavior of that control without totally replacing the style. An example of such a key is <xref:System.Windows.Controls.ToolBar.ButtonStyleKey%2A>.
|
||||
|
||||
The WPF merged dictionary feature introduces additional considerations for key uniqueness and key lookup behavior. For more information, see [Merged Resource Dictionaries](../framework/wpf/advanced/merged-resource-dictionaries.md).
|
||||
The WPF merged dictionary feature introduces additional considerations for key uniqueness and key lookup behavior. For more information, see [Merged resource dictionaries](../net/wpf/systems/xaml-resources-merged-dictionaries.md).
|
||||
|
||||
## XAML 2009
|
||||
|
||||
@@ -95,7 +96,7 @@ keyObject
|
||||
|
||||
### XAML Values
|
||||
|
||||
|||
|
||||
| Value | Description |
|
||||
|-|-|
|
||||
|`keyObject`|Object element for the object that is used as the key for a given `object` in a specialized dictionary.|
|
||||
|
||||
@@ -111,6 +112,6 @@ keyObject
|
||||
|
||||
## See also
|
||||
|
||||
- [XAML Resources](../net/wpf/fundamentals/xaml-resources-define.md)
|
||||
- [Resources and Code](../framework/wpf/advanced/resources-and-code.md)
|
||||
- [Overview of XAML resources (WPF .NET)](../net/wpf/systems/xaml-resources-overview.md)
|
||||
- [Resources in code (WPF .NET)](../net/wpf/systems/xaml-resources-and-code.md)
|
||||
- [StaticResource Markup Extension](../framework/wpf/advanced/staticresource-markup-extension.md)
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: "XML Character Entities and XAML"
|
||||
description: "Describes how special characters are handled in XAML and general considerations for other XML concepts in XAML."
|
||||
ms.date: "03/30/2017"
|
||||
f1_keywords:
|
||||
- "&"
|
||||
@@ -59,7 +60,7 @@ XAML handles XML processing instructions according to XML specifications, which
|
||||
|
||||
## See also
|
||||
|
||||
- [XAML Overview (WPF)](../net/wpf/fundamentals/xaml.md)
|
||||
- [XAML overview (WPF .NET)](../net/wpf/xaml/index.md)
|
||||
- [Markup Extensions and WPF XAML](../framework/wpf/advanced/markup-extensions-and-wpf-xaml.md)
|
||||
- [XamlName Grammar](xamlname-grammar.md)
|
||||
- [White-space processing in XAML](white-space-processing.md)
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: "xml:space Handling in XAML"
|
||||
description: "Describes the xml:space attribute and how it affects white-space processing behavior within an object element."
|
||||
ms.date: "03/30/2017"
|
||||
helpviewer_keywords:
|
||||
- "XAML [XAML Services], xml:space attribute"
|
||||
@@ -39,4 +40,4 @@ For a complete discussion of white-space processing in XAML, see [White-space pr
|
||||
## See also
|
||||
|
||||
- [White-space processing in XAML](white-space-processing.md)
|
||||
- [XAML Overview (WPF)](../net/wpf/fundamentals/xaml.md)
|
||||
- [XAML overview (WPF .NET)](../net/wpf/xaml/index.md)
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: "x:Null Markup Extension"
|
||||
description: "Describes how the x:Null markup extension is handled by XAML."
|
||||
ms.date: "03/30/2017"
|
||||
f1_keywords:
|
||||
- "NullExtension"
|
||||
@@ -44,5 +45,5 @@ Note that `null` is not necessarily the initial unset value for a reference-type
|
||||
## See also
|
||||
|
||||
- <xref:System.Windows.DependencyProperty.UnsetValue>
|
||||
- [XAML Overview (WPF)](../net/wpf/fundamentals/xaml.md)
|
||||
- [XAML overview (WPF .NET)](../net/wpf/xaml/index.md)
|
||||
- [Markup Extensions and WPF XAML](../framework/wpf/advanced/markup-extensions-and-wpf-xaml.md)
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: "x:Shared Attribute"
|
||||
description: "Describes the x:Shared attribute and how it modifies the WPF resource-retrieval behavior."
|
||||
ms.date: "03/30/2017"
|
||||
helpviewer_keywords:
|
||||
- "XAML [XAML Services], x:Shared attribute"
|
||||
@@ -29,7 +30,7 @@ In WPF, the default `x:Shared` condition for resources is `true`. This condition
|
||||
|
||||
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](../net/wpf/fundamentals/xaml-resources-define.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 [Overview of XAML resources (WPF .NET)](../net/wpf/systems/xaml-resources-overview.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 XAML Services and its XAML readers.
|
||||
|
||||
@@ -48,5 +49,5 @@ In WPF, `x:Shared` is only valid under the following conditions:
|
||||
## See also
|
||||
|
||||
- <xref:System.Windows.ResourceDictionary>
|
||||
- [XAML Resources](../net/wpf/fundamentals/xaml-resources-define.md)
|
||||
- [Overview of XAML resources (WPF .NET)](../net/wpf/systems/xaml-resources-overview.md)
|
||||
- [Base Elements](../framework/wpf/advanced/base-elements.md)
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: "x:Type Markup Extension"
|
||||
description: "Describes how the x:Type markup extension is used in XAML. The x:Type markup extension specifies a CLR object."
|
||||
ms.date: "03/30/2017"
|
||||
f1_keywords:
|
||||
- "x:TypeExtension"
|
||||
@@ -33,7 +34,7 @@ Supplies the CLR <xref:System.Type> object that is the underlying type for a spe
|
||||
|
||||
## XAML Values
|
||||
|
||||
|||
|
||||
| Value | Description |
|
||||
|-|-|
|
||||
|`prefix`|Optional. A prefix that maps a non-default XAML namespace. Specifying a prefix is frequently not necessary. See Remarks.|
|
||||
|`typeNameValue`|Required. A type name resolvable to the current default XAML namespace; or the specified mapped prefix if `prefix` is supplied.|
|
||||
@@ -81,6 +82,6 @@ In WPF, you can use XAML 2009 features but only for loose XAML (XAML that is not
|
||||
## See also
|
||||
|
||||
- <xref:System.Windows.Style>
|
||||
- [Styling and Templating](../net/wpf/fundamentals/styles-templates-overview.md)
|
||||
- [XAML Overview (WPF)](../net/wpf/fundamentals/xaml.md)
|
||||
- [Styles and templates (WPF .NET)](../net/wpf/controls/styles-templates-overview.md)
|
||||
- [XAML overview (WPF .NET)](../net/wpf/xaml/index.md)
|
||||
- [Markup Extensions and WPF XAML](../framework/wpf/advanced/markup-extensions-and-wpf-xaml.md)
|
||||
|
||||
Reference in New Issue
Block a user