如何将PowerShell窗体按钮绑定至外部PS脚本并加载执行？

Absolutely! You can totally bind buttons in your main PowerShell form to external script files to launch other forms—this is a super common way to keep your GUI projects organized and modular. Let me break down exactly how to make this work for your scenario.

First, split your code into separate files for cleanliness:

• Main-Form.ps1: Your main form with all the top-level buttons
• Ad-Form.ps1: The script that defines and shows the "Create AD User" form

Wrap the AD form logic in a function so you can easily call it from the main script. This also lets you test the AD form independently if you need to. Here's an example:

function Show-ADUserForm {
    # Load required .NET assemblies (only needed if not already loaded by the main script)
    Add-Type -AssemblyName System.Windows.Forms
    Add-Type -AssemblyName System.Drawing

    # Create the AD user form
    $adForm = New-Object System.Windows.Forms.Form
    $adForm.Text = "Create New AD User"
    $adForm.Size = New-Object System.Drawing.Size(350, 250)
    $adForm.StartPosition = "CenterScreen"

    # Add example controls (customize these to fit your needs)
    $firstNameLabel = New-Object System.Windows.Forms.Label
    $firstNameLabel.Text = "First Name:"
    $firstNameLabel.Location = New-Object System.Drawing.Point(20, 30)
    $adForm.Controls.Add($firstNameLabel)

    $firstNameBox = New-Object System.Windows.Forms.TextBox
    $firstNameBox.Location = New-Object System.Drawing.Point(100, 30)
    $firstNameBox.Size = New-Object System.Drawing.Size(200, 20)
    $adForm.Controls.Add($firstNameBox)

    # Add more controls (last name, username, etc.) here...

    # Show the form and wait for user input
    $adForm.ShowDialog() | Out-Null
}

# Let the script run the form directly if executed on its own (for testing)
if ($MyInvocation.InvocationName -ne '&') {
    Show-ADUserForm
}

In your Main-Form.ps1, you'll need to load the external script and assign a click event to your button that calls the Show-ADUserForm function. Here's how:

# Load required .NET assemblies
Add-Type -AssemblyName System.Windows.Forms
Add-Type -AssemblyName System.Drawing

# Load the AD form script (use the correct path if it's in a different folder)
. .\Ad-Form.ps1

# Create the main form
$mainForm = New-Object System.Windows.Forms.Form
$mainForm.Text = "Main Administration Tool"
$mainForm.Size = New-Object System.Drawing.Size(400, 300)
$mainForm.StartPosition = "CenterScreen"

# Create the "Create Ad User" button
$adUserButton = New-Object System.Windows.Forms.Button
$adUserButton.Text = "Create Ad User"
$adUserButton.Location = New-Object System.Drawing.Point(20, 20)
$adUserButton.Size = New-Object System.Drawing.Size(140, 35)

# Assign the click event: when clicked, launch the AD form
$adUserButton.Add_Click({
    Show-ADUserForm  # This calls the function from Ad-Form.ps1
})

$mainForm.Controls.Add($adUserButton)

# Add your other two buttons here following the same pattern...

# Show the main form
$mainForm.ShowDialog() | Out-Null

• Double-check the script path: If Ad-Form.ps1 isn't in the same folder as Main-Form.ps1, use a full absolute path (like C:\PowerShellScripts\Ad-Form.ps1) instead of the relative path.
• Assembly loading: You can load System.Windows.Forms and System.Drawing just once in the main script—since the main script runs first, the assemblies will already be available when the AD form loads.
• Testing: Run Ad-Form.ps1 directly to test the form without opening the main form—this saves time when debugging the AD form's controls.

That's all there is to it! When you click the "Create Ad User" button in your main form, it'll trigger the function from the external script and pop up the AD user form exactly as you want.

内容的提问来源于stack exchange，提问作者Fardin Barashi