Same param specified twice discards parameter variable attributes

[mklement0]

Steps to reproduce

Create script ./script.ps1 as follows:

param([ValidateSet('bar', 'baz')] [string] $Foo)

# Output count of attributes.
(Get-Variable Foo).Attributes.Count

Then dot-source the script twice:

> . ./script.ps1; . ./script.ps1

Expected behavior

3
3

Actual behavior

3
0

Repeated dot-sourcing happens implicitly when you run your code repeatedly in the ISE, for instance.

Environment data

PowerShell Core v6.0.0-alpha (v6.0.0-alpha.16) on Darwin Kernel Version 16.4.0: Thu Dec 22 22:53:21 PST 2016; root:xnu-3789.41.3~3/RELEASE_X86_64

[SteveL-MSFT]

Don't have to dot-source

PS /home/steve> param([ValidateSet('bar', 'baz')] [string] $Foo)                            
PS /home/steve>                                                                             
PS /home/steve> # Output count of attributes.                                               
PS /home/steve> (Get-Variable Foo).Attributes.Count                                         
3
PS /home/steve> param([ValidateSet('bar', 'baz')] [string] $Foo)                            
PS /home/steve>                                                                             
PS /home/steve> # Output count of attributes.                                               
PS /home/steve> (Get-Variable Foo).Attributes.Count                                         
0

[lzybkr]

@SteveL-MSFT - the interactive prompt is equivalent to dot sourcing. Dot sourcing just means - don't create a new scope. The interactive prompt executes everything in global scope which also means no new scope is created.

[microsoft-github-policy-service]

This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.

[microsoft-github-policy-service]

This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.

[microsoft-github-policy-service]

This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.

[microsoft-github-policy-service]

This issue has been marked as "No Activity" as there has been no activity for 6 months. It has been closed for housekeeping purposes.