Add source and project files for Hyper-V agent.
As a general guid, *.cs files are source,
*.csproj file is Visual Studio project that contains build settings and instructions,
settings of all kinds are in XML,
*.Designer.* files are generated by Visual Studio for its various editors.

More details...
packages.config references NuGet library packages that the project relies on.
Settings for the agent are held in AgentShell.settings in XML format
AgentShell.Designer.cs includes wrappers for easy access to the settings.
Service1 subytypes ServiceBase, which provides it with all the hooks to be run as a Windows Service, which is the Windows equivalent of a Daemon process.  The name is unfortunate, and may change.  The service uses a trick whereby it can be run as a Console application for debugging in addition to being capable of being run as a Windows Service.  The reason is that you cannot run a Windows Service direcdly.  It has to be started by the Service Control Manager (SCM), which gets in the way of developers.  The decision to run as a console application or a Windows Service is taken in Program.cs on the basis of a command line arguement.
Strongly typed wrappers for WMI class that were generated by the mgmtclassgen.exe program.
Details of how to generate the code at the command line are in Readme.txt.  However, it is easier to do this from VisualStudio's ServerExplorer.  Right click on the Wmi Management Class to get the option to generate the code.
The classes are limited in their usefulness, because the generated code is poor in quality and limited in functionality.  However, they do avoid a lot of time consuming work involved in writing parameter marshalling for invoking WMI methods, and they get the Class name strings correct.
Contains rewrite of Python code to control Hyper-V.  The rewrite uses C# to make Wmi invocations directly.
The code flow has been updated to simplify the operations.  However, C# calls to WMI use the System.Management objects, which mean the code is pretty verbose.  To deal with this problem, steps have been separated into different functions to hide the complexity of WMI.
Unit tests for methods to control Hyper-V.  However, they have become more like integration tests.
Attributes mark the class and methods to test, we launch these using the Visual STudio 'Test Explorer'