Update debug-win command

[ForNeVeR]

After long thoughts I've asked this question on StackOverflow and got the answer.

We have to use PowerShell for this functionality to work properly, but that shouldn't be a problem because today there are no up-to-date Windows systems without PowerShell.

PowerShell itself will create two child processes - one in a job object with PowerShell process itself, and second with derived IO (thanks to -Wait switch).

After I press Ctrl-C, the second process will be killed, and after that PowerShell process will terminate itself (because it was blocked on the killed process), and OS will terminate all processes in the same job as PowerShell (so everyone will be killed, nice).

It will close issue #5 and improve debugging experience on Windows.

[rdner]

But what if we don't have PowerShell on the machine? I think we need to save previous approach as the fallback, don't you think so?

[ForNeVeR]

What kind of Windows machine today really have no PowerShell? I think everything starting from (and including) Windows XP SP2 have it out of the box.

But if you have any examples of it - then we can leave previous, legacy script as a fallback.

[rdner]

I think we should use the universal solution, like

WHERE powershell && IF %ERRORLEVEL% EQ 0 (powershell -Command \"Start-Process -NoNewWindow node ./build.js; Start-Process -NoNewWindow -Wait node ./server.js\") ELSE (start /B node ./build.js && start /B node ./server.js)

I'm not sure it works, I'll check it later (or maybe you could help me).

[rdner]

As I know PowerShell was not a part of Windows before Windows 8, am I right?

[ForNeVeR]

Well, I don't like that solution, that's terrible mess of cmd and powershell :(

And PowerShell was built in starting from Windows XP SP2 (I'm 100% sure that it is built in Win 7 at least; Wikipedia says it was there from XP SP2).

I think that the best strategy is to make a separate script for legacy software users and do not mix old and new approach.

[rdner]

Well, I agree and I don't think we need to support the WinXP users since node.js doesn't in fact.

[rdner]

👍

[rdner]

Could you re-open this PR with develop as a destination branch?

[ForNeVeR]

Regarding nodejs - in fact it does (BTW, we are still talking about io.js; nodejs support for XP wasn't dropped at all); check the comment at the bottom of the page you linked.

Okay, I'll rebase my code now, gimme a minute.

[ForNeVeR]

Rebase done.

[ForNeVeR]

Ah, I cannot change the target branch without reopening PR. >_<