From e41982f0e5e1fc6b05635506061a1f5979b9ce23 Mon Sep 17 00:00:00 2001 From: Sean Wheeler Date: Fri, 17 May 2024 15:06:37 -0500 Subject: [PATCH] Fix links --- .../About/about_Parameter_Binding.md | 16 ++++++++-------- .../About/about_Parameter_Binding.md | 16 ++++++++-------- .../About/about_Parameter_Binding.md | 16 ++++++++-------- .../About/about_Parameter_Binding.md | 16 ++++++++-------- .../deep-dives/visualize-parameter-binding.md | 12 ++++++------ 5 files changed, 38 insertions(+), 38 deletions(-) diff --git a/reference/5.1/Microsoft.PowerShell.Core/About/about_Parameter_Binding.md b/reference/5.1/Microsoft.PowerShell.Core/About/about_Parameter_Binding.md index 34b48419489c..ff9e1d4830a9 100644 --- a/reference/5.1/Microsoft.PowerShell.Core/About/about_Parameter_Binding.md +++ b/reference/5.1/Microsoft.PowerShell.Core/About/about_Parameter_Binding.md @@ -35,10 +35,10 @@ After binding command-line arguments, PowerShell tries to bind any pipeline input. There are two ways that values are bound from the pipeline. Parameters that accept pipeline input have one or both of the following attributes: -- [ValueFromPipeline][01] - The value from the pipeline is bound to the +- [ValueFromPipeline][02] - The value from the pipeline is bound to the parameter based on its type. The type of the argument must match the type of the parameter. -- [ValueFromPipelineByPropertyName][02] - The value from the pipeline is bound +- [ValueFromPipelineByPropertyName][03] - The value from the pipeline is bound to the parameter based on its name. The object in the pipeline must have a property that matches the name of the parameter or one of its aliases. The type of the property must match or be convertible to the type of the @@ -78,7 +78,7 @@ PowerShell tries to bind pipeline input in the following order: ## Visualize parameter binding Troubleshooting parameter binding issues can be challenging. You can use the -[Trace-Command][03] cmdlet to visualize the parameter binding process. The +[Trace-Command][04] cmdlet to visualize the parameter binding process. The following example shows how to trace the parameter binding for a simple pipeline. @@ -91,10 +91,10 @@ Trace-Command -PSHost -Name ParameterBinding -Expression { The output shows every step of the parameter binding process for the commands in the **Expression**. The output can be verbose, but it can help you understand why a parameter isn't being bound as expected. For a complete -example, see [Visualize parameter binding][04]: +example, see [Visualize parameter binding][01]: -[01]: about_functions_advanced_parameters.md#valuefrompipeline-argument -[02]: about_functions_advanced_parameters.md#valuefrompipelinebypropertyname-argument -[03]: xref:Microsoft.PowerShell.Utility.Trace-Command -[04]: /powershell/scripting/learn/deep-dives/visualize-parameter-binding +[01]: /powershell/scripting/learn/deep-dives/visualize-parameter-binding +[02]: about_functions_advanced_parameters.md#valuefrompipeline-argument +[03]: about_functions_advanced_parameters.md#valuefrompipelinebypropertyname-argument +[04]: xref:Microsoft.PowerShell.Utility.Trace-Command diff --git a/reference/7.2/Microsoft.PowerShell.Core/About/about_Parameter_Binding.md b/reference/7.2/Microsoft.PowerShell.Core/About/about_Parameter_Binding.md index ae2aad09b430..a38d95153017 100644 --- a/reference/7.2/Microsoft.PowerShell.Core/About/about_Parameter_Binding.md +++ b/reference/7.2/Microsoft.PowerShell.Core/About/about_Parameter_Binding.md @@ -35,10 +35,10 @@ After binding command-line arguments, PowerShell tries to bind any pipeline input. There are two ways that values are bound from the pipeline. Parameters that accept pipeline input have one or both of the following attributes: -- [ValueFromPipeline][01] - The value from the pipeline is bound to the +- [ValueFromPipeline][02] - The value from the pipeline is bound to the parameter based on its type. The type of the argument must match the type of the parameter. -- [ValueFromPipelineByPropertyName][02] - The value from the pipeline is bound +- [ValueFromPipelineByPropertyName][03] - The value from the pipeline is bound to the parameter based on its name. The object in the pipeline must have a property that matches the name of the parameter or one of its aliases. The type of the property must match or be convertible to the type of the @@ -78,7 +78,7 @@ PowerShell tries to bind pipeline input in the following order: ## Visualize parameter binding Troubleshooting parameter binding issues can be challenging. You can use the -[Trace-Command][03] cmdlet to visualize the parameter binding process. The +[Trace-Command][04] cmdlet to visualize the parameter binding process. The following example shows how to trace the parameter binding for a simple pipeline. @@ -91,10 +91,10 @@ Trace-Command -PSHost -Name ParameterBinding -Expression { The output shows every step of the parameter binding process for the commands in the **Expression**. The output can be verbose, but it can help you understand why a parameter isn't being bound as expected. For a complete -example, see [Visualize parameter binding][04]: +example, see [Visualize parameter binding][01]: -[01]: about_functions_advanced_parameters.md#valuefrompipeline-argument -[02]: about_functions_advanced_parameters.md#valuefrompipelinebypropertyname-argument -[03]: xref:Microsoft.PowerShell.Utility.Trace-Command -[04]: /powershell/scripting/learn/deep-dives/visualize-parameter-binding +[01]: /powershell/scripting/learn/deep-dives/visualize-parameter-binding +[02]: about_functions_advanced_parameters.md#valuefrompipeline-argument +[03]: about_functions_advanced_parameters.md#valuefrompipelinebypropertyname-argument +[04]: xref:Microsoft.PowerShell.Utility.Trace-Command diff --git a/reference/7.4/Microsoft.PowerShell.Core/About/about_Parameter_Binding.md b/reference/7.4/Microsoft.PowerShell.Core/About/about_Parameter_Binding.md index facec8730244..96f089744676 100644 --- a/reference/7.4/Microsoft.PowerShell.Core/About/about_Parameter_Binding.md +++ b/reference/7.4/Microsoft.PowerShell.Core/About/about_Parameter_Binding.md @@ -35,10 +35,10 @@ After binding command-line arguments, PowerShell tries to bind any pipeline input. There are two ways that values are bound from the pipeline. Parameters that accept pipeline input have one or both of the following attributes: -- [ValueFromPipeline][01] - The value from the pipeline is bound to the +- [ValueFromPipeline][02] - The value from the pipeline is bound to the parameter based on its type. The type of the argument must match the type of the parameter. -- [ValueFromPipelineByPropertyName][02] - The value from the pipeline is bound +- [ValueFromPipelineByPropertyName][03] - The value from the pipeline is bound to the parameter based on its name. The object in the pipeline must have a property that matches the name of the parameter or one of its aliases. The type of the property must match or be convertible to the type of the @@ -78,7 +78,7 @@ PowerShell tries to bind pipeline input in the following order: ## Visualize parameter binding Troubleshooting parameter binding issues can be challenging. You can use the -[Trace-Command][03] cmdlet to visualize the parameter binding process. The +[Trace-Command][04] cmdlet to visualize the parameter binding process. The following example shows how to trace the parameter binding for a simple pipeline. @@ -91,10 +91,10 @@ Trace-Command -PSHost -Name ParameterBinding -Expression { The output shows every step of the parameter binding process for the commands in the **Expression**. The output can be verbose, but it can help you understand why a parameter isn't being bound as expected. For a complete -example, see [Visualize parameter binding][04]: +example, see [Visualize parameter binding][01]: -[01]: about_functions_advanced_parameters.md#valuefrompipeline-argument -[02]: about_functions_advanced_parameters.md#valuefrompipelinebypropertyname-argument -[03]: xref:Microsoft.PowerShell.Utility.Trace-Command -[04]: /powershell/scripting/learn/deep-dives/visualize-parameter-binding +[01]: /powershell/scripting/learn/deep-dives/visualize-parameter-binding +[02]: about_functions_advanced_parameters.md#valuefrompipeline-argument +[03]: about_functions_advanced_parameters.md#valuefrompipelinebypropertyname-argument +[04]: xref:Microsoft.PowerShell.Utility.Trace-Command diff --git a/reference/7.5/Microsoft.PowerShell.Core/About/about_Parameter_Binding.md b/reference/7.5/Microsoft.PowerShell.Core/About/about_Parameter_Binding.md index 367e4c0eeccf..2459e42451c3 100644 --- a/reference/7.5/Microsoft.PowerShell.Core/About/about_Parameter_Binding.md +++ b/reference/7.5/Microsoft.PowerShell.Core/About/about_Parameter_Binding.md @@ -35,10 +35,10 @@ After binding command-line arguments, PowerShell tries to bind any pipeline input. There are two ways that values are bound from the pipeline. Parameters that accept pipeline input have one or both of the following attributes: -- [ValueFromPipeline][01] - The value from the pipeline is bound to the +- [ValueFromPipeline][02] - The value from the pipeline is bound to the parameter based on its type. The type of the argument must match the type of the parameter. -- [ValueFromPipelineByPropertyName][02] - The value from the pipeline is bound +- [ValueFromPipelineByPropertyName][03] - The value from the pipeline is bound to the parameter based on its name. The object in the pipeline must have a property that matches the name of the parameter or one of its aliases. The type of the property must match or be convertible to the type of the @@ -78,7 +78,7 @@ PowerShell tries to bind pipeline input in the following order: ## Visualize parameter binding Troubleshooting parameter binding issues can be challenging. You can use the -[Trace-Command][03] cmdlet to visualize the parameter binding process. The +[Trace-Command][04] cmdlet to visualize the parameter binding process. The following example shows how to trace the parameter binding for a simple pipeline. @@ -91,10 +91,10 @@ Trace-Command -PSHost -Name ParameterBinding -Expression { The output shows every step of the parameter binding process for the commands in the **Expression**. The output can be verbose, but it can help you understand why a parameter isn't being bound as expected. For a complete -example, see [Visualize parameter binding][04]: +example, see [Visualize parameter binding][01]: -[01]: about_functions_advanced_parameters.md#valuefrompipeline-argument -[02]: about_functions_advanced_parameters.md#valuefrompipelinebypropertyname-argument -[03]: xref:Microsoft.PowerShell.Utility.Trace-Command -[04]: /powershell/scripting/learn/deep-dives/visualize-parameter-binding +[01]: /powershell/scripting/learn/deep-dives/visualize-parameter-binding +[02]: about_functions_advanced_parameters.md#valuefrompipeline-argument +[03]: about_functions_advanced_parameters.md#valuefrompipelinebypropertyname-argument +[04]: xref:Microsoft.PowerShell.Utility.Trace-Command diff --git a/reference/docs-conceptual/learn/deep-dives/visualize-parameter-binding.md b/reference/docs-conceptual/learn/deep-dives/visualize-parameter-binding.md index 82e61d37b8da..da28f6aac886 100644 --- a/reference/docs-conceptual/learn/deep-dives/visualize-parameter-binding.md +++ b/reference/docs-conceptual/learn/deep-dives/visualize-parameter-binding.md @@ -22,11 +22,11 @@ following attributes: parameter or one of its aliases. The type of the property must match or be convertible to the type of the parameter. -For more information about parameter binding, see [about_Parameter_Binding][04]. +For more information about parameter binding, see [about_Parameter_Binding][03]. ## Use `Trace-Command` to visualize parameter binding -Troubleshooting parameter binding issues can be challenging. You can use the [Trace-Command][03] +Troubleshooting parameter binding issues can be challenging. You can use the [Trace-Command][04] cmdlet to visualize the parameter binding process. Consider the following scenario: You have a directory with two text files, `file1.txt` and @@ -253,7 +253,7 @@ CALLING EndProcessing ``` -[01]: about_functions_advanced_parameters.md#valuefrompipeline-argument -[02]: about_functions_advanced_parameters.md#valuefrompipelinebypropertyname-argument -[03]: xref:Microsoft.PowerShell.Utility.Trace-Command -[04]: /powershell/modules/microsoft.powershell.core/about/about_parameter_binding +[01]: /powershell/modules/microsoft.powershell.core/about/about_functions_advanced_parameters#valuefrompipeline-argument +[02]: /powershell/modules/microsoft.powershell.core/about/about_functions_advanced_parameters#valuefrompipelinebypropertyname-argument +[03]: /powershell/modules/microsoft.powershell.core/about/about_parameter_binding +[04]: xref:Microsoft.PowerShell.Utility.Trace-Command