如何配置任务以在VSC IDE(版本2.0.0)中启动.ps1-脚本?

时间:2019-05-07 15:45:28

标签: json powershell visual-studio-code mql

我想使用Visual Studio Code IDE(“ VSC”)在MQL中(而不是在本机MetaEditor IDE中)进行开发,如下所述:How to code & compile MQL5 in Visual Studio

我的问题涉及到编译过程,该过程由一个VSC任务组成,该任务调用一个PowerShell脚本,该脚本依次调用MetaEditor.exe,然后动态将要传递的当前.mq5-文件传递给该脚本。编译(这就是使用任务的原因)。

当我直接运行PowerShell脚本(通过选择其代码并点击 F8 )时,一切正常,但是当我尝试通过指定的VSC任务运行它时,出现错误...

  

终端进程终止,退出代码为:1

...即使我选择PowerShell作为VSC使用的默认外壳程序(而不是cmd,这也是我的相应设置:“ terminal.integrated.shell.windows”:“ C:\ Windows \ System32 \ WindowsPowerShell \ v1.0 \ powershell.exe“)。

这是.json格式的VSC任务,版本2.0.0 ,我正在谈论:

{
    // See https://go.microsoft.com/fwlink/?LinkId=733558
    // for the documentation about the tasks.json format
    "version": "2.0.0",
    "tasks": [
        {
            "label": "Compile-MQL",
            "type": "shell",
            "command": "C:\\Users\\Username\\AppData\\Roaming\\MetaQuotes\\Terminal\\D0E8209F77C8CF37AD8BF550E51FF075\\MQL5\\Compile-MQL.ps1 ${file}",
            "presentation": {
                "echo": true,
                "reveal": "always",
                "focus": false,
                "panel": "shared",
                "showReuseMessage": false
            },
            "group": {
                "kind": "build",
                "isDefault": true
            }
        }
    ]
}

有人可以适应我上面的VSC任务,使其开箱即用吗?

@postanote:请不要在此处再次复制粘贴类似问题的答案,因为很遗憾,我无法将版本0.1.0转换为2.0.0(或任何其他偏差),我敢肯定可以快速调整我的几行代码,以便他们立即起作用的人...

非常感谢!

PS:这是上面提到的PowerShell脚本(与 F8 一起使用):

#gets the File To Compile as an external parameter... Defaults to a Test file...
Param($FileToCompile = "C:\Users\Username\AppData\Roaming\MetaQuotes\Terminal\D0E8209F77C8CF37AD8BF550E51FF075\MQL5\Experts\Advisors\ExpertMACD.mq5")

#cleans the terminal screen and sets the log file name...
Clear-Host
$LogFile = $FileToCompile + ".log"
& "C:\Users\Username\AppData\Roaming\MetaQuotes\Terminal\D0E8209F77C8CF37AD8BF550E51FF075\MQL5\compile.bat" "C:\Program Files\MetaTrader 5\metaeditor64.exe" "$FileToCompile" "$LogFile" "C:\Users\Username\AppData\Roaming\MetaQuotes\Terminal\D0E8209F77C8CF37AD8BF550E51FF075\MQL5"

#before continue check if the Compile File has any spaces in it...
if ($FileToCompile.Contains(" ")) {
    "";"";
    Write-Host "ERROR!  Impossible to Compile! Your Filename or Path contains SPACES!" -ForegroundColor Red;
    "";
    Write-Host $FileToCompile -ForegroundColor Red;
    "";"";
    return;
}

#first of all, kill MT Terminal (if running)... otherwise it will not see the new compiled version of the code...
Get-Process -Name terminal64 -ErrorAction SilentlyContinue |
    Where-Object {$_.Id -gt 0} |
    Stop-Process

#fires up the Metaeditor compiler...
& "C:\Program Files\MetaTrader 5\metaeditor64.exe" /compile:"$FileToCompile" /log:"$LogFile" /inc:"C:\Users\Username\AppData\Roaming\MetaQuotes\Terminal\D0E8209F77C8CF37AD8BF550E51FF075\MQL5" | Out-Null

#get some clean real state and tells the user what is being compiled (just the file name, no path)...
"";"";"";"";""
$JustTheFileName = Split-Path $FileToCompile -Leaf
Write-Host "Compiling........: $JustTheFileName"
""

#reads the log file. Eliminates the blank lines. Skip the first line because it is useless.
$Log = Get-Content -Path $LogFile |
       Where-Object {$_ -ne ""} |
       Select-Object -Skip 1

#Green color for successful Compilation. Otherwise (error/warning), Red!
$WhichColor = "Red"
$Log | ForEach-Object {
    if ($_.Contains("0 error(s), 0 warning(s)")) {
        $WhichColor="Green"
    }
}

#runs through all the log lines...
$Log | ForEach-Object {
     #ignores the ": information: error generating code" line when ME was successful
     if (-not $_.Contains("information:")) {
          #common log line... just print it...
          Write-Host $_ -ForegroundColor $WhichColor
     }
}

#get the MT Terminal back if all went well...
if ($WhichColor -eq "Green") {
    & "c:\program files\metatrader 5\terminal64.exe"
}

PS2:MetaEditor IDE可以为installed for free together with MetaTrader 5 here

1 个答案:

答案 0 :(得分:1)

与此同时,我自己也找到了原因:我的默认Windows Powershell安全设置阻止执行.ps1-script。解决方案是以管理员身份运行PowerShell(Win + x→Windows PowerShell(管理员))并运行命令

Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope CurrentUser

→确认。

以下是有兴趣的读者的一些背景信息:

About Execution Policies

Set Execution Policy