@gmitch64 : Assuming you have a PowerShell script that you call directly has e.g. .\HelloWorld.ps1, then you can suppress as follows:

[System.Diagnostics.CodeAnalysis.SuppressMessageAttribute("PSUseDeclaredVarsMoreThanAssignments", "")]
Param()

Set-StrictMode -Version Latest


$DefaultDHCPServer = "server"
$DefaultDNSServer = "server"
$DefaultDomainName = "domain"

Please let me know if this answered your question.

Thanks, that seems to make it work as I expected it.

What I am missing is my understanding of my I need to specify a Param() for it, and why it needs to be the first lines in the script. The more you learn, the more there is that you need to learn :)

Thanks very much for the solution, and for giving me more work to do :)

@gmitch64 You're welcome, I am glad it worked out for you. PSSA works by parsing PowerShell scripts as the PowerShell AST (abstract syntax tree), which are publicly available classes from the internals of PowerShell itself. The code that parses the script is here and you see here that it parses the script as scriptblock and function asts, therefore the Param() helps the parser to identify the whole script file as a function. But I am sure that this parsing code could be improved so that the Param() is not needed any more. At the moment, ideas are also floating around in issue 849 to enhance suppression to be able to enable/disable suppresions just for a few lines (similar to ReSharper warnings).
If your question is answered satisfactorily, then please close the issue.

@bergmeister Thanks for the explanation. I'll upvote issue 849, as it would be useful I think. I'll mark this issue as closed.

Thanks.