PR Summary

This PR includes changes in Build.psm1, packaging.psm1 and the release build template files.

• For Build.psm1, -ForMinimalSize is added to Start-PSBuild to build self-contained application for "linux-x64", "win7-x64", or "osx-x64" runtimes. It reduces the size of package by:

  • Avoid CrossGen PowerShell and all other library assemblies.
  • Not include the Graphical Host and the WPF/WinForm stuff it pulls in.
  • Remove symbol files (.pdb) and XML document files (.xml)

• For packaging.psm1, min-size is added as a new value for -Type parameter of Start-PSPackage.

• For Windows release build, a new build configuration minSize is added, to build and packaging the min-size package.
  For Linux release build, -TarMinSize is added to PowerShellPackage.ps1 as well as build.json to build and package for the min-size package.

The min-size package has the -gc suffix to indicate that it's for the Guest Config team. In the Azure Blob, the min-size packages are uploaded to the container with the -gc suffix, not in the main package maintainer (e.g. v7-2-0-preview-4), so that they don't get uploaded to the GitHub release page.

Here is the release build run: https://dev.azure.com/mscodehub/PowerShellCore/_build/results?buildId=175764&view=results

The package size is reduced:

• Windows (x64-zip): from 97mb to 45.3mb
• Linux (x64-tar.gz): from 63.4mb to 40.6mb

PR Context

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • None
  • OR
  • Experimental feature(s) needed
    • Experimental feature name(s):
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    • Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.