如何在C#解决方案资源中创建PowerShell脚本？部署路径问题求解

Great question! Let's break this down into two practical, deployable solutions that eliminate your hardcoded C:\ path dependency.

1. Add the PowerShell Script to Your C# Solution (As a Deployable File) #

Absolutely, you can (and should) add a new PowerShell script directly to your C# project. Here's how to set it up so it works across devices:

• Add the script to your project: Right-click your project in Solution Explorer → Add → New Item → Select "PowerShell Script", name it something like MyDeploymentScript.ps1, and write your logic there.
• Configure deployment settings: Select the script file in Solution Explorer, open its Properties window, and set Copy to Output Directory to Copy if newer (or Copy always). This ensures the script gets copied to the same folder as your app's executable when you build/deploy.
• Use a dynamic path in C#: Instead of hardcoding C:\..., fetch the app's running directory and build the script path dynamically:

using System.IO;
using System.Reflection;
using System.Management.Automation;

// Get the directory where your app is currently running
string appDirectory = Path.GetDirectoryName(Assembly.GetExecutingAssembly().Location);
// Build the path to your deployed script
string scriptPath = Path.Combine(appDirectory, "MyDeploymentScript.ps1");

// Execute the script
using (var powerShell = PowerShell.Create())
{
    powerShell.AddScript(File.ReadAllText(scriptPath));
    var executionResults = powerShell.Invoke();
    
    // Handle results or errors here (check powerShell.Streams.Error if needed)
}

2. Embed the Script as an Assembly Resource (No External File) #

If you want to avoid having a separate .ps1 file altogether, embed the script directly into your C# assembly:

• Mark the script as an embedded resource: Select your .ps1 file in Solution Explorer, open Properties, set Build Action to Embedded Resource.
• Read and execute the embedded script: Fetch the script content directly from your app's assembly without needing a file path:

using System.IO;
using System.Reflection;
using System.Management.Automation;

// Note: Resource name = Your project's root namespace + script filename (e.g., "MyApp.MyDeploymentScript.ps1")
string resourceName = $"{Assembly.GetExecutingAssembly().GetName().Name}.MyDeploymentScript.ps1";

using (Stream resourceStream = Assembly.GetExecutingAssembly().GetManifestResourceStream(resourceName))
{
    if (resourceStream == null)
        throw new FileNotFoundException("Embedded script resource not found", resourceName);
    
    using (StreamReader reader = new StreamReader(resourceStream))
    {
        string scriptContent = reader.ReadToEnd();
        
        // Execute the inline script content
        using (var powerShell = PowerShell.Create())
        {
            powerShell.AddScript(scriptContent);
            var executionResults = powerShell.Invoke();
            
            // Handle results/errors here
        }
    }
}

Which Option Should You Choose? #

• Use the deployable file method if you want users to be able to modify the script without recompiling your C# app.
• Use the embedded resource method if you want to fully encapsulate the script within your app (no loose files to manage).

Both approaches completely eliminate the need for hardcoded local paths, making your app work reliably on any device it's deployed to.

内容的提问来源于stack exchange，提问作者Josh Pulda