Moving to interactive service
Its a bit hard to review this with all the refactoring going on. Would it be possible to split this with the refactoring and cleanup moved to a future PR? I thought the last commit would pretty much covers all that is needed for the iservice-based startup to work.
But my idea was exactly this - there are few commits for refactoring without any functional changes (like splitting functionality into different files) and this last commit is switching to iservice.
Here you can get an installer with necessary changes to all components. At least here it works fine :)
I think this service should start the interactive service, if it is not running already.
I think this service should start the interactive service, if it is not running already.
It is now depends on interactive service https://github.com/OpenVPN/openvpn-build/pull/849/files so Windows should start iservice first.
Ping @selvanair @d12fk
Doxygen would be nice, but a bit more excessive commit messages, describing the things done in the commit, are missing often.
Doxygen would be nice, but a bit more excessive commit messages, describing the things done in the commit, are missing often.
Made some commit messages more descriptive and added some XML comments - this is a standard way to document code in C# and is natively supported by Visual Studio (unlike Doxygen). Also, Doxygen is able to parse them.