This coudl fix #937

No more http->socks5 transform.

Remove some debug output

This fix the proxy issue on win10 insider preview.

Fix #926

Let TCP stack find a free port for us

Signed-off-by: Syrone Wong <wong.syrone@gmail.com>

Signed-off-by: Syrone Wong <wong.syrone@gmail.com>

Otherwise we will update proxy twice.

Use singleton mode for hotkey callbacks.

This gives us the possibility to chose SS server based on dest address.

Refine RNG usage

- Create instance once, bind it to ShadowsocksController

Signed-off-by: Syrone Wong <wong.syrone@gmail.com>

Signed-off-by: Syrone Wong <wong.syrone@gmail.com>

Signed-off-by: Syrone Wong <wong.syrone@gmail.com>

Signed-off-by: Syrone Wong <wong.syrone@gmail.com>

Also, fix typo in ProxyForm

Signed-off-by: Syrone Wong <wong.syrone@gmail.com>

Get rid of tricky registry handling

Several files come from https://code.msdn.microsoft.com/windowsapps/CSWebBrowserWithProxy-c8535715/view/SourceCode

Signed-off-by: Syrone Wong <wong.syrone@gmail.com>

Signed-off-by: Syrone Wong <wong.syrone@gmail.com>

Signed-off-by: Syrone Wong <wong.syrone@gmail.com>

Shadowsocks don't need to reconnect, which is the software's
responsibility to retry.

Signed-off-by: Syrone Wong <wong.syrone@gmail.com>

- Use readonly object as lock

Info from stackoverflow:

If I want to be sure that it will be locked for all threads inside my
application:
The lock object has to be static, if it locks access to static state.
Otherwise it has to be instance, because there's no need to lock state of
one class instance, and prevent other threads to work with another class
instance at the same time.

everyone says that the object has to be "readonly" I didn't found the
reason
Well, it doesn't have to be. This is just a best practice, which helps you
to avoid errors.

Signed-off-by: Syrone Wong <wong.syrone@gmail.com>

It is better to log them.

Signed-off-by: Syrone Wong <wong.syrone@gmail.com>

Signed-off-by: Syrone Wong <wong.syrone@gmail.com>

Signed-off-by: Syrone Wong <wong.syrone@gmail.com>