There are a number of obstacles which prevent us from following the instructions on ​dev/win32.

For some dependencies, it is just a question of doing more manual work than running the 64-bit version of the installer, as is the case for ​setuptools and ​python wmi.

Then there's the problem that by default, you can't compile 64-bit programs with distutils and VC 2008... (see ​http://bugs.python.org/issue7511 and use this patch: ​http://bugs.python.org/file17959/vcvars4.diff - why isn't this merged and released??)

Unfortunately, other dependencies are even harder to deal with:

• ​pygtk (or even just plain GTK for that matter) do not provide 64-bit installers at present, and building from source is too tedious: see ​this discussion for details.
• ​gstreamer does not provide a 64-bit version, all the bindings are for 32-bit python only at present...

Important:

• it needs a man page - this is a debian requirement: all public commands (ie: /usr/bin/) need a man page, even if it is a small one that refers to another one

More minor issues:

• how do you create your config files? this needs to be documented somewhere, maybe providing an example config with comments in /usr/share/winswitch/launcher-example/
• I've removed the default values from LauncherSession to ensure they are populated correctly from file - the code should ensure the values make sense (port>0, host.len>0)
• LauncherClient should show a warning if the session fails to start
• file mime-type mapping so users can double click on them and have the software automatically launched
• dealing with ssh-tunnels (totally non-trivial)

Split from #88 : what is needed is just the TCP network code ported to MS Windows as per ​ossbuild ticket 166