Starting ADB Server results in a dangling process as the server is treated as a child process

[BenWoodford]

Not sure what the best resolution is here, I think perhaps UseShellExecute should be true when starting the server?

The main issue is it ends up leaving TCP sockets open and things like that if not cleaned up properly, as the ADB Server is running as a child of the .NET project, so the OS won't clean things up - despite the parent process ending it doesn't truly end until the ADB Server is killed as well

I assume it's start-server anyway, it could also be a hung command but I don't think I have any of those in my project...