Invoke-Compile errorCode assert is returning non zero after successful .NET solution compile

[lholman]

When calling the default Invoke-Commit task in OneBuild, ultimately the Invoke-Compile task is executed which is returning a non zero errorCode value after a successful .NET solution compile and failing the OneBuild, see below.

 Elapsed 00:00:00.30
At C:\Development\ConsoleApplication1\OneBuild.build.ps1:96 char:1
+ task Invoke-Compile Invoke-HardcoreClean, Set-VersionNumber, {
At C:\Development\ConsoleApplication1\OneBuild.build.ps1:43 char:1
+ task Invoke-Commit Invoke-Compile, Invoke-UnitTests, New-Packages, Undo-Check
edO ...
WARNING: No VersionNumber.xml found at: C:\Development\ConsoleApplication1, gen
erating default VersionNumber.xml (major = 0 and minor = 1).
WARNING: VersionNumber.xml file found, reading to set [major] and [minor] versi
on numbers.
WARNING: Setting [major] version number to: 0.
WARNING: Setting [minor] version number to: 1.
Build FAILED. 6 tasks, 2 errors, 4 warnings 00:00:03.3173317
Assert-Build : Assertion failed.At
C:\Development\ConsoleApplication1\OneBuild.build.ps1:109 char:2
+     assert ($errorCode -eq 0)
    + CategoryInfo          : InvalidOperation: (:) [Assert-Build], Exception
    + FullyQualifiedErrorId : Assert-Build

##teamcity[buildStatus status='FAILURE' text='{build.status.text} in execution']

C:\Development\ConsoleApplication1 [master +5 ~5 -2 !]>