问是否有办法使Powershell对函数的输出使用特定的格式？

EN

- That `*.ps1xml` _files_ are invariably needed for such definitions is unfortunate; [GitHub issue #7845](https://github.com/PowerShell/PowerShell/issues/7845) asks for an in-memory, API-based alternative (which for _type_ data already exists, via the [`Update-TypeData`](https://learn.microsoft.com/powershell/module/microsoft.powershell.utility/update-typedata) cmdlet).

- However, in the context of [_modules_](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_Modules), the need for files is less inconvenient, as they can be bundled with the module and are automatically loaded when referenced from the [module manifest](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_Module_Manifests)'s `FormatsToProcess` entry.

- If it is `[pscustomobject]` instances that the formatting should apply to, you need to (a) _choose_ a unique (virtual) type name and (b) assign it to the `[pscustomobject]` instances via PowerShell's [ETS (Extended Type System)](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_Types.ps1xml); e.g.:

    - For `[pscustomobject]` instances created by the [`Select-Object`](https://learn.microsoft.com/powershell/module/microsoft.powershell.utility/select-object) cmdlet:

    - For `[pscustomobject]` _literals_, specify the type name via a `PSTypeName` entry:

- If the commands that rely on this formatting data are defined in a _module_, you can incorporate the file into your module so that it is automatically automatically when the module is imported.

- For help on authoring such files, see:

    - [Formatting File Overview](https://learn.microsoft.com/en-us/powershell/scripting/developer/format/formatting-file-overview)
    - [Format XML Reference](https://learn.microsoft.com/en-us/powershell/scripting/developer/format/format-schema-xml-reference)

- As you can see, creating the XML for the formatting definitions is verbose and cumbersome, even without additional settings, such as column width and alignment.

- A better, but more elaborate solution would be to package your function in a [_module_](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_Modules) into whose folder you can place the `*.ps1mxl` file (e.g., `SearchAdUserResult.Format.ps1xml`) and then instruct PowerShell to load the file on module import, via the `FormatsToProcess` key in the [module manifest](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/new-modulemanifest) (`*.psd1`) - e.g., `FormatsToProcess = 'SearchAdUserResult.Format.ps1xml'`

function Search-ADUser {
  param (
    $Name,
    [ValidateNotNullOrEmpty()][string[]]$Properties = @('Enabled', 'SamAccountName', 'Name', 'emailAddress', 'proxyAddresses')
  )

  # The self-chosen ETS type name.
  $etsTypeName = 'SearchAdUserResult'

  # Create the formatting data on demand.
  if (-not (Get-FormatData -ErrorAction Ignore $etsTypeName)) {

    # Create a temporary file with formatting definitions to pass to 
    # Update-FormatData below.
    $tempFile = Join-Path ([IO.Path]::GetTempPath()) "$etsTypeName.Format.ps1xml"

    # Define a table view with all 5 properties.
    @"
<Configuration>
<ViewDefinitions>
    <View>
      <Name>$etsTypeName</Name>
      <ViewSelectedBy>
        <TypeName>$etsTypeName</TypeName>
      </ViewSelectedBy>
      <TableControl>
        <TableRowEntries>
          <TableRowEntry>
            <TableColumnItems>
              <TableColumnItem>
                <PropertyName>Enabled</PropertyName>
              </TableColumnItem>
              <TableColumnItem>
                <PropertyName>SamAccountName</PropertyName>
              </TableColumnItem>
              <TableColumnItem>
                <PropertyName>Name</PropertyName>
              </TableColumnItem>
              <TableColumnItem>
                <PropertyName>emailAddress</PropertyName>
              </TableColumnItem>
              <TableColumnItem>
                <PropertyName>proxyAddresses</PropertyName>
              </TableColumnItem>
            </TableColumnItems>
          </TableRowEntry>
        </TableRowEntries>
      </TableControl>
    </View>
  </ViewDefinitions>
</Configuration>
"@ > $tempFile

    # Load the formatting data into the current session.
    Update-FormatData -AppendPath $tempFile

    # Clean up.
    Remove-Item $tempFile
  }

  # Call Get-ADUser and assign the self-chosen ETS type name to the the output.
  # Note: To test this with a custom-object literal, use the following instead of the Get-ADUser call:
  #      [pscustomobject] @{ Enabled = $true; SamAccountName = 'jdoe'; Name = 'Jane Doe'; emailAddress = 'jdoe@example.org'; proxyAddresses = 'janedoe@example.org' }
  Get-ADUser -Filter ('name -like "*{0}*"' -F $Name) -Properties $Properties | Select-Object $Properties | ForEach-Object {
     $_.pstypenames.Insert(0, $etsTypeName); $_
  }

}

Enabled SamAccountName Name     emailAddress     proxyAddresses
------- -------------- ----     ------------     --------------
True    jdoe           Jane Doe jdoe@example.org janedoe@example.org