Most likely it is the result of the exception in the user code.
This is what happens when you build WixSharp in VS:
- VS builds your assembly (projects executable)
- VS runs WixSharp.targets from the NuGet package:
<Exec Command=""$(TargetPath)" "/MBSBUILD:$(ProjectName)"" WorkingDirectory="$(ProjectDir)"/>
As the result your assembly gets executed and if it doesn't exit cleanly then VS returns a failure exit code (e.g. -532462766) assumed by VS/OS. The code itself has no meaning for the user as usually the assembly entry point routine doesn't control exit code
static void Main()
However if any WiX error is encountered then it is caught by
and printed in the VS output window. On the other hand if it is the user code raises the unhanded exception then the error info is lost. If it is the case then you can easily
fix this by putting your Main implementation in the try-catch or better yet place
at the start and you will be able to see the error under debugger.