Confusing Cosmetic Commandline issue

Found a minor, but confusing behaviour when using wybuild.exe on the command line.After execution, it returns to the command line and then prints wybuild's message. This makes it look like wybuild is stilll running and waiting for a keypress, but it's actually the commandline that's waiting for input.

Looks a bit like this:

<Samplecommandline>

C:\temp>"C:\Program Files\wyBuild\wybuild.exe" c:\projects\test.wyp /bu -add= "c:\temp\list.xml"C:\temp>Updates built successfully.

_ (blinking cursor is here)

</Samplecommandline>

Couldn't resist the alliteration in the subject. 🙂

Hey Frederik,

This is actually unavoidable for several long technical reasons. But the gist of it is, when a .NET app functions as both a GUI and a commandline app you get weird quirks like this.

We used to have a fix where a new prompt would appear below "Updates built successfully", but this caused several problems on build servers that run under the System account. Thus we had to remove the "fix" that actually broke more than it fixed.

To sum up, we're aware of the problem, but it won't be fixed soon. In the future we will have a separate commandline-only update builder that companies can deploy on their build servers, and remove the commandline building from wyBuild.exe completely.

Sorry for the confusion.

I noticed that wybuild is still running while it returned to the command line, still building updates in the background. This would've be a problem if I was scripting through simple batch files. Fortunately I'm using MSBuild and since the Exec task hooks into process.Exited event, that should synchronise correctly on process termination, ie. when everything has been built.

Are there any other gotcha's with this approach?

I noticed that wybuild is still running while it returned to the command line, still building updates in the background.

"Updates built successfully." appears only after the update has been built successfully. Then wyBuild quits as fast as it can (it's not "zero time" -- that's impossible -- but it is under a second on modern PCs). Other than the bit of cleanup wyBuild has to do when it exits, no other threads or processes are running after "Updates built successfully."

Are you sure you're not calling wyBuild multiple times?

If this is still happening, can you give me instructions on how to reproduce this behavior.

Not really having this issue anymore.

Reply
Discard post