A) PREPARE
--------------------
1) get visual studio 2013 community edition (it's free)
2) get github for windows and click "clone in desktop" on this page
https://github.com/ZeroK-RTS/Zero-K-Infrastructure3) open the Zero-K.sln in visual studio
B) DO IT
------------
Refactor the code so that
1) There are two "Connection" classes one for ZKL server and other for "TasClient" class used in clients. That should be trivial.
2) move the "server" connection copy to ZKL server library instead of common libraries
3) change plasmashared and lobbyclient libs so that they target .NET 4.0 client profile. They wont'c ompile
4) Install BCL Async library through nuget for lobbyclient and reinstall existing nuget packages. Nuget is here
5) refactor EventHandlers of TasClient and TasClient legacy to older style (non generic) you can check github how they looked in the past
6) factor in further changes. You might need to change some methods like Task.WhenAll to TaskEx.WhenAll and move helper functions across libs.
7) change target of ZKL to .NET 4.0 client profile
C) TEST IT
============
1) test it locally by setting up to start multiple projects at once
and start zero-k website, zero-k lobby server, springie, zero-k lobby and optionally "fixer" configured to run Nubsimulator test. If it can handle thousand of people without issues and lobby still works it's all set
2) commit/make a pull request. After it get's merged to master, re-test everything again on test.zero-k.info
3) when it gets merged to stable -> PROFIT
This is open source, I'm not your slave, you have the same power I do.
Want to run ZK on outdated insecure OS that
nobody appears to support for new products??
Fine, but don't scream and force people to do the hard stuff for you. Either spend money or your own time by doing it yourself.