VS Code调试PowerShell Azure Function触发OmniSharp异常求助

调试PowerShell 7版本的v4模型Azure Function时，按F5启动调试立即抛出异常，配置的func: host start前置任务可正常运行，但调试流程直接中断。
涉及环境：

• VS Code：1.68.0
• Azure Core Tools：v4
• PowerShell：7

现有调试配置（launch.json）：

{
  "version": "0.2.0",
  "configurations": [   
    
    {
      "name": "Attach to PowerShell Functions",
      "type": "PowerShell",
      "request": "attach",
      "customPipeName": "AzureFunctionsPSWorker",
      "runspaceId": 1,
      "preLaunchTask": "func: host start"      
    }    
  ]
}

测试函数run.ps1代码：

using namespace System.Net

# Input bindings are passed in via param block.
param($Request, $TriggerMetadata)

# Write to the Azure Functions log stream.
Write-Host "PowerShell HTTP trigger function processed a request."

# Interact with query parameters or the body of the request.
$name = $Request.Query.Name
if (-not $name) {
    $name = $Request.Body.Name
}

$body = "This HTTP triggered function executed successfully. Pass a name in the query string or in the request body for a personalized response."

if ($name) {
    $body = "Hello, $name. This HTTP triggered function executed successfully."
}

# Associate values to output bindings by calling 'Push-OutputBinding'.
Push-OutputBinding -Name Response -Value ([HttpResponseContext]@{
    StatusCode = [HttpStatusCode]::OK
    Body = $body
})

1. 时序不匹配：preLaunchTask仅负责启动func host主进程，PowerShell语言工作进程（PS Worker）是主进程启动后异步拉起的，原配置没有预留worker初始化时间，在命名管道还未创建时就发起attach连接，直接触发连接失败异常。
2. 配置参数错误：原配置中runspaceId固定写为1，Azure Functions v4版本的PowerShell Worker启动后初始运行空间ID不固定为1，会导致attach时找不到目标运行空间；同时未配置调试超时时间，默认超时阈值过短。
3. 缺少Worker调试开关：项目配置中没有开启PS Worker的自定义命名管道调试模式，worker启动后不会创建AzureFunctionsPSWorker名称的管道供调试器连接。
4. 前置任务标记缺失：func: host start任务没有配置后台任务匹配规则，VS Code会在任务执行瞬间就判定任务完成，立刻触发attach动作，完全不等host和worker初始化。

• 第一步：修改项目根目录的local.settings.json，添加PowerShell Worker调试环境变量，强制worker启动时创建指定名称的调试管道：

{
  "IsEncrypted": false,
  "Values": {
    "AzureWebJobsStorage": "UseDevelopmentStorage=true",
    "FUNCTIONS_WORKER_RUNTIME": "powershell",
    "FUNCTIONS_WORKER_RUNTIME_VERSION": "7.2",
    "PSWorkerCustomPipeName": "AzureFunctionsPSWorker"
  }
}

• 第二步：更新.vscode/launch.json配置，修正runspace匹配规则，添加30秒调试连接超时：

{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Attach to PowerShell Functions",
      "type": "PowerShell",
      "request": "attach",
      "customPipeName": "AzureFunctionsPSWorker",
      "runspaceId": -1,
      "preLaunchTask": "func: host start",
      "timeout": 30000
    }
  ]
}

配置说明：runspaceId: -1表示自动匹配PS Worker的默认运行空间，避免固定ID不匹配的问题；30000毫秒超时预留了充足的host和worker初始化时间。

• 第三步：更新.vscode/tasks.json中的func: host start任务，标记为后台任务并添加启动完成匹配规则，确保VS Code在host完全启动后再触发attach：

{
  "version": "2.0.0",
  "tasks": [
    {
      "label": "func: host start",
      "type": "shell",
      "command": "func host start",
      "isBackground": true,
      "problemMatcher": [
        {
          "owner": "azureFunctions",
          "pattern": {
            "regexp": "^.*$"
          },
          "background": {
            "activeOnStart": true,
            "beginsPattern": "^.*Starting Job host.*$",
            "endsPattern": "^.*Job host started.*$"
          }
        }
      ]
    }
  ]
}

• 第四步：清理残留进程后验证：关闭所有打开的VS Code终端，执行以下PowerShell命令清理后台残留的func进程，再按F5启动调试即可正常进入断点，不会出现启动即异常的问题。

Get-Process func -ErrorAction SilentlyContinue | Stop-Process -Force

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