deadlydog

personal statement

My name is Daniel Schroeder and I love to create software for other developers, and software that increases efficiency and productivity. Automate everything!

activity stream

May 25, 2016 - Invoke-MsBuild PowerShell Module - MOVED TO GITHUB: Commented work item: Invoke-msbuild getting error when triggered through build definition

May 25, 2016 - Invoke-MsBuild PowerShell Module - MOVED TO GITHUB: Commented work item: Allow for 32bit version of msbuild.exe

May 25, 2016 - Invoke-MsBuild PowerShell Module - MOVED TO GITHUB: Edited wiki: Home

May 25, 2016 - Invoke-MsBuild PowerShell Module - MOVED TO GITHUB: Edited wiki: Home

May 25, 2016 - Invoke-MsBuild PowerShell Module - MOVED TO GITHUB: Posted to discussion: Blocking on completion

May 25, 2016 - Invoke-MsBuild PowerShell Module - MOVED TO GITHUB: Posted to discussion: Redirect output

May 25, 2016 - Invoke-MsBuild PowerShell Module - MOVED TO GITHUB: Posted to discussion: Migrate to GitHub?

May 24, 2016 - Invoke-MsBuild PowerShell Module - MOVED TO GITHUB: Pushed 83a9aba657a93ccee1f7ff8c21e71707ffa9ea14, - Updated script to v2.0.0. - Updated tests to use new v2 syntax and add tests for new features. - Updated auto publish script to handle release notes better. ------------------------- 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). - 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

May 24, 2016 - Invoke-MsBuild PowerShell Module - MOVED TO GITHUB: Committed 83a9aba657a93ccee1f7ff8c21e71707ffa9ea14, - Updated script to v2.0.0. - Updated tests to use new v2 syntax and add tests for new features. - Updated auto publish script to handle release notes better. ------------------------- 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). - 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

May 4, 2016 - AHK Command Picker: Committed deb8d72dab3107990945d826b3c46f577691d630, - Updated version from 1.3.1 to 1.3.2. - Changed file paths to use an absolute path (via A_ScriptDir) instead of a relative path to fix issues when the working directory is not the same as the directory that the script is in.