java - PowerShell 中手动执行和编程执行的输出不同

Question

手动运行与编程运行时，我从同一命令获得两个不同的输出，但我不明白为什么。

有问题的命令:

powershell -Command "Get-Module -ListAvailable"

在命令提示符下手动运行时，我得到以下输出:

U:\> powershell -Command "Get-Module -ListAvailable"

Directory: C:\Program Files\WindowsPowerShell\Modules

ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Binary     1.0.0.1    PackageManagement                   {Find-Package, Get-Package, Get-PackageProvider, Get-PackageSource...}
Script     1.0.0.1    PowerShellGet                       {Install-Module, Find-Module, Save-Module, Update-Module...}
Binary     6.5.1.6... VMware.DeployAutomation             {Add-DeployRule, Add-ProxyServer, Add-ScriptBundle, Copy-DeployRule...}
Binary     6.5.1.6... VMware.ImageBuilder                 {Add-EsxSoftwareDepot, Add-EsxSoftwarePackage, Compare-EsxImageProfile, Export-EsxImageProfile...}
Manifest   6.5.4.7... VMware.PowerCLI
Binary     6.5.4.6... VMware.VimAutomation.Cis.Core       {Connect-CisServer, Disconnect-CisServer, Get-CisService}
Binary     6.5.1.5... VMware.VimAutomation.Cloud          {Add-CIDatastore, Connect-CIServer, Disconnect-CIServer, Get-Catalog...}
Manifest   6.5.4.6... VMware.VimAutomation.Common
Binary     6.5.2.6... VMware.VimAutomation.Core           {Add-PassthroughDevice, Add-VirtualSwitchPhysicalNetworkAdapter, Add-VMHost, Add-VMHostNtpServer...}
Binary     6.5.4.7... VMware.VimAutomation.HA             Get-DrmInfo
Binary     7.1.0.5... VMware.VimAutomation.HorizonView    {Connect-HVServer, Disconnect-HVServer}
Binary     6.5.1.5... VMware.VimAutomation.License        Get-LicenseDataManager
Binary     2.0.0.6... VMware.VimAutomation.Nsxt           {Connect-NsxtServer, Disconnect-NsxtServer, Get-NsxtService}
Binary     6.5.1.5... VMware.VimAutomation.PCloud         {Connect-PIServer, Disconnect-PIServer, Get-PIComputeInstance, Get-PIDatacenter}
Manifest   1.0.0.5... VMware.VimAutomation.Sdk            {Get-PSVersion, Get-InstallPath}
Binary     6.5.1.5... VMware.VimAutomation.Srm            {Connect-SrmServer, Disconnect-SrmServer}
Binary     6.5.4.7... VMware.VimAutomation.Storage        {Add-KeyManagementServer, Copy-VDisk, Export-SpbmStoragePolicy, Get-KeyManagementServer...}
Script     1.1        VMware.VimAutomation.StorageUtility Update-VmfsDatastore
Binary     6.5.1.5... VMware.VimAutomation.Vds            {Add-VDSwitchPhysicalNetworkAdapter, Add-VDSwitchVMHost, Export-VDPortGroup, Export-VDSwitch...}
Binary     6.5.4.7... VMware.VimAutomation.Vmc            {Connect-Vmc, Disconnect-Vmc, Get-VmcService, Connect-VmcServer...}
Binary     6.5.1.5... VMware.VimAutomation.vROps          {Connect-OMServer, Disconnect-OMServer, Get-OMAlert, Get-OMAlertDefinition...}
Binary     6.5.1.5... VMware.VumAutomation                {Add-EntityBaseline, Copy-Patch, Get-Baseline, Get-Compliance...}

Directory: C:\Windows\system32\WindowsPowerShell\v1.0\Modules

ModuleType Version Name                             ExportedCommands
---------- ------- ----                             ----------------
Manifest   1.0.0.0 AppLocker                        {Set-AppLockerPolicy, Get-AppLockerPolicy, Test-AppLockerPolicy, Get-AppLockerFileInformation...}
Manifest   1.0.0.0 BitsTransfer                     {Add-BitsFile, Remove-BitsTransfer, Complete-BitsTransfer, Get-BitsTransfer...}
Manifest   1.0.0.0 CimCmdlets                       {Get-CimAssociatedInstance, Get-CimClass, Get-CimInstance, Get-CimSession...}
Script     1.0.0.0 ISE                              {New-IseSnippet, Import-IseSnippet, Get-IseSnippet}
Manifest   1.0.0.0 Microsoft.PowerShell.Archive     {Compress-Archive, Expand-Archive}
Manifest   3.0.0.0 Microsoft.PowerShell.Diagnostics {Get-WinEvent, Get-Counter, Import-Counter, Export-Counter...}
Manifest   3.0.0.0 Microsoft.PowerShell.Host        {Start-Transcript, Stop-Transcript}
Manifest   3.1.0.0 Microsoft.PowerShell.Management  {Add-Content, Clear-Content, Clear-ItemProperty, Join-Path...}
Script     1.0     Microsoft.PowerShell.ODataUtils  Export-ODataEndpointProxy
Manifest   3.0.0.0 Microsoft.PowerShell.Security    {Get-Acl, Set-Acl, Get-PfxCertificate, Get-Credential...}
Manifest   3.1.0.0 Microsoft.PowerShell.Utility     {Format-List, Format-Custom, Format-Table, Format-Wide...}
Manifest   3.0.0.0 Microsoft.WSMan.Management       {Disable-WSManCredSSP, Enable-WSManCredSSP, Get-WSManCredSSP, Set-WSManQuickConfig...}
Manifest   1.0.0.0 NetworkSwitchManager             {Disable-NetworkSwitchEthernetPort, Enable-NetworkSwitchEthernetPort, Get-NetworkSwitchEthernetPort, Remove-NetworkSwitchEthernetPortIPAddress...}
Manifest   1.1     PSDesiredStateConfiguration      {Set-DscLocalConfigurationManager, Start-DscConfiguration, Test-DscConfiguration, Publish-DscConfiguration...}
Script     1.0.0.0 PSDiagnostics                    {Disable-PSTrace, Disable-PSWSManCombinedTrace, Disable-WSManTrace, Enable-PSTrace...}
Binary     1.1.0.0 PSScheduledJob                   {New-JobTrigger, Add-JobTrigger, Remove-JobTrigger, Get-JobTrigger...}
Manifest   2.0.0.0 PSWorkflow                       {New-PSWorkflowExecutionOption, New-PSWorkflowSession, nwsn}
Manifest   1.0.0.0 PSWorkflowUtility                Invoke-AsWorkflow
Manifest   1.0.0.0 TroubleshootingPack              {Get-TroubleshootingPack, Invoke-TroubleshootingPack}

Directory: C:\opscode\chefdk\modules

ModuleType Version Name ExportedCommands
---------- ------- ---- ----------------
Script     0.0     chef {chef-apply, chef-client, chef-service-manager, chef-shell...}

当以编程方式运行时(通过 Java)，我得到以下输出:

ModuleType Name                      ExportedCommands
---------- ----                      ----------------
Binary     PackageManagement         {Find-Package, Get-Package, Get-PackageProvider, Get-PackageSource...}
Script     PowerShellGet             {Install-Module, Find-Module, Save-Module, Update-Module...}
Manifest   BitsTransfer              {Add-BitsFile, Remove-BitsTransfer, Complete-BitsTransfer, Get-BitsTrans...
Manifest   CimCmdlets                {Get-CimAssociatedInstance, Get-CimClass, Get-CimInstance, Get-CimSessio...
Script     ISE                       {New-IseSnippet, Import-IseSnippet, Get-IseSnippet}
Manifest   Microsoft.PowerShell.A... {Compress-Archive, Expand-Archive}
Manifest   Microsoft.PowerShell.D... {Get-WinEvent, Get-Counter, Import-Counter, Export-Counter...}
Manifest   Microsoft.PowerShell.Host {Start-Transcript, Stop-Transcript}
Manifest   Microsoft.PowerShell.M... {Add-Content, Clear-Content, Clear-ItemProperty, Join-Path...}
Script     Microsoft.PowerShell.O... Export-ODataEndpointProxy
Manifest   Microsoft.PowerShell.S... {Get-Acl, Set-Acl, Get-PfxCertificate, Get-Credential...}
Manifest   Microsoft.PowerShell.U... {Format-List, Format-Custom, Format-Table, Format-Wide...}
Manifest   Microsoft.WSMan.Manage... {Disable-WSManCredSSP, Enable-WSManCredSSP, Get-WSManCredSSP, Set-WSManQ...
Manifest   PSDesiredStateConfigur... {Set-DscLocalConfigurationManager, Start-DscConfiguration, Test-DscConfi...
Manifest   PSDiagnostics             {Start-Trace, Stop-Trace, Enable-WSManTrace, Disable-WSManTrace...}
Binary     PSScheduledJob            {New-JobTrigger, Add-JobTrigger, Remove-JobTrigger, Get-JobTrigger...}
Manifest   TroubleshootingPack       {Get-TroubleshootingPack, Invoke-TroubleshootingPack}
Script     chef                      {chef-apply, chef-client, chef-service-manager, chef-shell...}

编程运行的输出缺少“版本”列，并且只是可用模块的子集。

我想也许我以某种方式调用了两个不同的 PowerShell 可执行文件，因此我以手动和编程方式运行了 powershell -Command "$PSVersionTable"。

手动运行 powershell -Command "$PSVersionTable" 的输出:

Name                           Value
----                           -----
PSVersion                      5.0.10586.117
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.10586.117
CLRVersion                     4.0.30319.18444
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

以编程方式运行 powershell -Command "$PSVersionTable" 的输出:

Name                           Value
----                           -----
PSVersion                      5.0.10586.117
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.10586.117
CLRVersion                     4.0.30319.18444
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

所以我认为我正在运行相同的 PowerShell 可执行文件。

为什么运行相同的命令时会得到两个完全不同的输出？

用于以编程方式运行命令的实际 Java 代码:

public class Example {

    private void myMethod(String command) throws IOException {
        Process process = Runtime.getRuntime().exec(command);
        BufferedReader bufferedReader =
            new BufferedReader(new InputStreamReader(process.getInputStream()));

        String output = "";
        String line;
        while ((line = bufferedReader.readLine()) != null) {
            output += (line + "\n");
        }

        System.out.println((output.isEmpty() ?
                            "No output was received!!!" :
                            output));


        BufferedReader errorBufferedReader =
            new BufferedReader(new InputStreamReader(process.getErrorStream()));
        String errorOutput = "";
        while ((line = errorBufferedReader.readLine()) != null) {
            errorOutput += (line + "\n");
        }

        System.out.println((errorOutput.isEmpty() ?
                           "Nothing in the error output stream." :
                           errorOutput));
    }


    public static void main(String[] args) throws IOException {
        new Example().myMethod(
            "powershell -Command \"Get-Module -ListAvailable\"");
    }

}

Answer 1

我的猜测是，当从 Java 以编程方式调用 PowerShell 时，您不会获得格式化输出，或者由于某种原因不同版本具有不同的默认格式配置。

首先，一些背景知识:

在命令行运行 PowerShell 获得的输出由格式文件中的格式决定。这些都存储在 $PSHome\*.format.ps1xml 。 Get-Module返回 System.Management.Automation.PSModuleInfo 类型的对象。如果你运行Select-String -Pattern 'PSModuleInfo' -Path "$PSHome\*.format.ps1xml"您可以找到指定默认格式的位置。会有Table对于 Format-Table ，这是您通常获得的默认值。还有Wide对于 Format-Wide ，和List对于 Format-List 。您可以在 Get-Help about_Format.ps1xml 了解有关控制台输出格式的更多信息。 .

由于 PSModuleInfo 的默认输出是使用表格格式，您应该能够通过调用以下命令使您的 Java 与 PowerShell 匹配:

new Example().myMethod("powershell -Command \"Get-Module -ListAvailable | Format-Table\"");

或者可能:

new Example().myMethod("powershell -Command \"Get-Module -ListAvailable | Format-Table | Out-String\"");

或者甚至可能只是:

new Example().myMethod("powershell -Command \"Get-Module -ListAvailable | Out-String\"");

至于 Java 做了什么不同或者为什么它的格式不相似，恐怕我不知道。

您也可以随时执行以下操作:

new Example().myMethod("powershell -Command \"Get-Module -ListAvailable | Out-String\"");

您也可能会成功使用 Get-Module -ListAvailable | ConvertTo-Json -Compress -Depth 1或Get-Module -ListAvailable | ConvertTo-Xml -NoTypeInformation -As String -Depth 1或类似的，如果你想序列化你的输出。请记住，默认深度为 ConvertTo-Json为2，默认深度ConvertTo-Xml是 1，深度超过 3 的任何内容都会非常慢。