Comment Or Un-Comment Multiple Lines In PowerShell Script

You can use VSCode, Select the text you want, and from Edit Menu, select Toggle Comment Block.

vivek10688 

This is almost an open-ended question since it raises more questions than we can easily answer in short-form.

I'll start with a dangerously-simple statement: yes, it's possible to comment different sections, however, it would not be trivial to do so as there are many unintended consequences that could come from this.

My question though is, what are you really trying to achieve here? Are you really just looking for a way to run specific blocks - which is what your "if ($RestartNumber -le x)" suggests, or are the comments serving another purpose?

There's a number of ways you could approach this but I think your idea of using "if ($RestartNumber)" is probably good enough.

Option 1: A big, fat "while" loop

Nothing complex about this one.

Basically, you're simply putting your entire existing code block from your original post inside of a "where" loop, which makes use of a Read-Host prompt to retrieve whatever user input you need.

I'd go with a basic variation like the one below - purely in the interests of offering a little more control over exactly what executes, given using operators like "less than" or "greater than" implicitly mean you'll be running or skipping entire chains.

Example code

while (($UserInput = Read-Host -Prompt "Enter the code block numbers to execute - separated by commas, or enter Q to quit") -ne "q")
{
    if ([string]::IsNullOrWhiteSpace($UserInput))
    {
        # If nothing was input, go back to the start and re-prompt.
        continue;
    }

    # Remove any unexpected padding, etc. before breaking it up into an array for ease of reference in the subsequent "if" blocks.
    $Sections = [regex]::Replace($UserInput, "[^0-9,]", "", [System.Text.RegularExpressions.RegexOptions]::CultureInvariant).Split(",");

    # Code block 1
    if ($Sections.Contains("1"))
    {
        Write-Host "Hello from code block 1.";
    }

    # Code block 2
    if ($Sections.Contains("2"))
    {
        Write-Host "Hello from code block 2.";
    }
}

Example output from example code

Again, this is just a really basic hypothetical approach since I'm not 100 per cent clear on what you're really trying to achieve, and whether the comments are a "must have" or just a means to an end.

Option 2: Use metadata to control segmentation

Alternatively, you could go down the path of using metadata within the script to act as parsing indicators. You'd then read and parse the same file, choosing to execute (or comment, if there's some reason you must have this taking place) as you go.

This is a complex path, which I'm absolutely not going to codify as there's just too many "what ifs" to contend with, but the following should serve as an abstract example.

Here, we've:

• Put the code blocks into functions so that they don't auto-execute;
• Used the natively-supported "#region...#endregion" statements to also demarcate what constitutes a "code block" (i.e. the parsing routine would be looking for the number in the #region "tag";
• Once the parsing is done, you'll have some form of text stream (sting or similar), which you wold pass to something like either Invoke-Expression or dot-source the code block (both shown in the example below.)

#region Block 1
function CodeBlock1
{
    Write-Host "Hello from code block 1.";
}
#endregion

#region Block 2
function CodeBlock2
{
    Write-Host "Hello from code block 2.";
}
#endregion

# Now, write a bunch of code that reads and parses the file, saving it as a text stream.
# After that, use something like:
Invoke-Expression -Command $ParsedText;

# or (if you like doing things the hard way):
$Code = [scriptblock]::Create($ParsedText);
. $Code;

(Note: This code will not work - it's only demonstrating an abstract framework for the bullet points above)

There's probably other options but this is like going down the rabbit hole, so I'm going to stop here.

Cheers,

Lain