Get-Help does not work for script files containing using statements.

Steps to reproduce

Create a script file test.ps1 with the following content:

using namespace System.Management.Automation

<#
.SYNOPSIS
A simple script for problem reproduction.
#>
Param ($SampleParam)

Execute following command:

> Get-Help .\test.ps1

Expected behavior

Get-Help .\test.ps1

NAME
    ...\test.ps1

SYNOPSIS
    A simple script for problem reproduction.


SYNTAX
    ...\test.ps1 [[-SampleParam] <Object>] [<CommonParameters>]


DESCRIPTION


RELATED LINKS

REMARKS
    To see the examples, type: "Get-Help ...\test.ps1 -Examples"
    For more information, type: "Get-Help ...\test.ps1 -Detailed"
    For technical information, type: "Get-Help ...\test.ps1 -Full"

Actual behavior

> Get-Help .\test.ps1
test.ps1 [[-SampleParam] <Object>]

Environment data

Name                           Value
----                           -----
PSVersion                      7.1.0-preview.7
PSEdition                      Core
GitCommitId                    7.1.0-preview.7-10-g3effa204103460c996a8612aa70718fdf924047d
OS                             Microsoft Windows 10.0.18363
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

[doctordns]

I wish that Help was more intelligent - and gave an error when it fails rather than no output.

[jhoneill]

Comment based help must be the first or last thing in the file or in the block for a function, so it comes before the using statement

<#
.SYNOPSIS
A simple script for problem reproduction.
#>
using namespace System.Management.Automation
Param ($SampleParam)
[enum]::GetNames([actionPreference])

Works.

function test-this {
[alias("Test")]
<#
.SYNOPSIS
A simple script for problem reproduction.
#>
Param ($SampleParam)
}

Gives no help

function test-this {
<#
.SYNOPSIS
A simple script for problem reproduction.
#>
[alias("Test")]
Param ($SampleParam)
}

Works.

I would be careful with a change like this which will enable some behavior in new versions but neither works nor errors/warns in old ones. It seems logical to say those things should be allowed in any order. However when someone takes a script with an order which works in 7.1 and tries to run it on an earlier version they will go crazy trying to figure out why it doesn’t work in Windows PowerShell or in something with PowerShell 7.0.2 embedded (like .NET interactive) .

The rules that using can be preceded by comments, and comment based help must be first or last have been there since the features were introduced.