PowerShell/build.ps1

$BIN = "${pwd}/bin"

mkdir $BIN/Modules -ErrorAction SilentlyContinue

# Deploy PowerShell modules
cd $BIN/Modules
robocopy ../../test/Pester Pester /s /e
cd ../..

# Publish PowerShell
cd src/Microsoft.PowerShell.Linux.Host
dotnet publish --framework dnxcore50 --output $BIN
# Copy files that dotnet-publish does not currently deploy
cd ../..
Add build.ps1 for Windows 2016-01-15 19:41:56 +01:00			`$BIN = "${pwd}/bin"`

			`mkdir $BIN/Modules -ErrorAction SilentlyContinue`

			`# Deploy PowerShell modules`
			`cd $BIN/Modules`
Use Modules instead of SnapIns Proper deployment of the Modules we support allowed me to remove my work-arounds using the deprecated SnapIn system to load all PowerShell libraries via Modules. I still don't like that this is done in build scripts, but we need better asset support from .NET CLI to change how this is done. PowerShell.Utility now deploys the CoreClr manifest, so unsupported commands don't show up erroneously. 2016-01-30 00:33:23 +01:00			`robocopy ../../test/Pester Pester /s /e`
Add build.ps1 for Windows 2016-01-15 19:41:56 +01:00			`cd ../..`

			`# Publish PowerShell`
			`cd src/Microsoft.PowerShell.Linux.Host`
Add NOETW preprocessor definition to Automation This is necessary to disable Tracing on Core PowerShell until the reimplementation of the Eventing library is ported to CLI. 2016-02-03 01:45:16 +01:00			`dotnet publish --framework dnxcore50 --output $BIN`
Add build.ps1 for Windows 2016-01-15 19:41:56 +01:00			`# Copy files that dotnet-publish does not currently deploy`
			`cd ../..`