Skip to content

Releases: deadlydog/Invoke-MsBuild

Invoke-MsBuild v2.4.2

20 Apr 20:48
Compare
Choose a tag to compare
  • Fixed bug where MsBuild.exe would not be found on 32-bit Windows OSs.

Invoke-MsBuild v2.4.1

20 Apr 06:44
Compare
Choose a tag to compare
  • Fixed "CurrentCulture is a ReadOnly property" bug on computers running .Net 4.5.2 and lower.

Invoke-MsBuild v2.4.0

02 Apr 05:50
Compare
Choose a tag to compare
  • Added MsBuildFilePath and VisualStudioDeveloperCommandPromptFilePath script parameters, so users can pass in which versions they would like to use, instead of the script using the latest versions.
  • Fixed inverted bool logic that was causing the VS Command Prompt to never be used.

Invoke-MsBuild v2.3.1

01 Apr 23:50
Compare
Choose a tag to compare
  • Fixes to truly support VS 2017 MsBuild

Invoke-MsBuild v2.3.0

31 Mar 07:18
Compare
Choose a tag to compare
  • Added support to find and use Visual Studio 2017's MsBuild.exe.

Invoke-MsBuild v2.2.0

31 Mar 03:38
Compare
Choose a tag to compare
  • Added LogVerbosityLevel parameter to adjust the verbosity MsBuild uses to write to the log file.
  • Fixed bug that prevented us from finding msbuild.exe on some machines.

Invoke-MsBuild v2.1.0

21 Sep 05:52
Compare
Choose a tag to compare
  • Added new Use32BitMsBuild parameter to allow users to force the 32-bit version of MsBuild.exe to be used instead of the 64-bit version when both are available.

Invoke-MsBuild v2.0.0

25 May 07:47
Compare
Choose a tag to compare

First release of Invoke-MsBuild v2!

v2 has the following breaking changes from v1:

  • A hash table with several properties is returned instead of a simple $true/$false/$null value.
  • The GetLogPath switch is gone and replaced with the WhatIf switch.

New features in v2 include:

  • A build log file containing only build errors is created alongside the regular build log file.
  • The errors build log file can be auto-launched on build failure.
  • New switch has been added to show the build output in the calling scripts console window (does not work with some 3rd party consoles due to Start-Process cmdlet bug).
  • A hash table containing the following properties is now returned:
  • BuildSucceeded = $true if the build passed, $false if the build failed, and $null if we are not sure.
  • BuildLogFilePath = The path to the builds log file.
  • BuildErrorsLogFilePath = The path to the builds error log file.
  • ItemToBuildFilePath = The item that MsBuild is ran against.
  • CommandUsedToBuild = The full command that is used to invoke MsBuild. This can be useful for inspecting what parameters are passed to MsBuild.exe.
  • Message = A message describing any problems that were encoutered by Invoke-MsBuild. This is typically an empty string unless something went wrong.
  • MsBuildProcess = The process that was used to execute MsBuild.exe.

Changes to make when updating from v1 to v2:

  • To capture/display the build success result, you must change:
    Invoke-MsBuild ...
    to:
    (Invoke-MsBuild ...).BuildSucceeded
  • To get the path where the log file will be created, you must change:
    Invoke-MsBuild ... -GetLogPath
    to:
    (Invoke-MsBuild ... -WhatIf).BuildLogFilePath