-
-
Notifications
You must be signed in to change notification settings - Fork 60
Build Scripts in Projects
These scripts are for pure PowerShell script projects. The following tasks are automated:
- Clean the project directory
- Run tests and compare results with expected
- Build the help file (PowerShell MAML format)
- Convert markdown files to HTML for packages
- Create packages
These scripts are examples of mixed build tools: Invoke-Build and MSBuild work together and call each other. See how the configuration parameter is passed in both directions.
The task Build calls MSBuild in order to build the C# project:
exec { MSBuild Src\Mdbc.csproj /t:Build /p:Configuration=$Configuration }
The task PostBuild is called by MSBuild as the post-build event, it copies the just built module and its satellite files to one of the PowerShell module directories, so that it is ready to use/debug after the build. The post-build command line is:
PowerShell.exe -NoProfile Invoke-Build PostBuild $(ProjectDir)\..\.build.ps1 -Configuration $(ConfigurationName)
Or even simpler with ib.cmd which also bypasses execution policy restrictions:
ib PostBuild $(ProjectDir)\..\.build.ps1 -Configuration $(ConfigurationName)
Other tasks are typical: clean, test, build and test help, create packages. Both projects use Invoke-Build for testing, each test is represented by a task in a test build script.
OneBuild is a modular set of convention based .NET solution build scripts written in PowerShell, relying on Invoke-Build for task automation. See OneBuild for more details.
This project is a collection of PowerShell issues described by markdown files, demo scripts, and test scripts. There is nothing to build here. The build script is for testing, generating the index, and other routine tasks.
This project maintains the complex build system where Invoke-Build and MSBuild work together in the hierarchy of projects with Invoke-Build scripts, MSBuild scripts (C++ and C# projects), and Visual Studio solutions.
Parent project scripts dispatch common tasks like Build, Install, Clean to child scripts, some of them dispatch these tasks further to their children.
One of the scripts in this hierarchy is a build task library which is imported
by other build scripts. Another point of interest is use of property
. It gets
parent script values in child scripts, parents do not have to to specify them
explicitly on task dispatching.
Some red-gate projects use Invoke-Build scripts:
- Concepts
- Script Tutorial
- Incremental Tasks
- Partial Incremental Tasks
- How Build Works
- Special Variables
- Build Failures
- Build Analysis
- Parallel Builds
- Persistent Builds
- Portable Build Scripts
- Using for Test Automation
- Debugging Tips
- VSCode Tips
Helpers
- Invoke Task from VSCode
- Generate VSCode Tasks
- Invoke Task from ISE
- Resolve MSBuild
- Show Build Trees
- Show Build Graph
- Argument Completers
- Invoke-Build.template
Appendix