Quoting TechTarget

Check out this three part article written by Andrew Kutz.

The preferred mechanism for programmatically interacting with VI3 is the SDK, not the commands available in the ESX COS (such as the suite of commands prefixed with "esxcfg" found in /usr/sbin). The SDK is very powerful, and its power can be harnessed with another equally powerful tool, .NET. In this article, I will describe the beginning steps you must take as you start down the path toward leveraging the VI3 SDK with .NET using C#.

The first step to leverage the VI3 SDK with .NET is to understand the VI3 SDK. This text is but one part in a series of articles that will explain how to use a complex piece of software, and this article should not be thought of as the golden standard for reference material on the subject. This text is meant to be a companion to VMware's own documentation, such as the "VMware Infrastructure Getting Started Guide," "VMware Infrastructure Programming Guide," and the "VMware Infrastructure SDK Reference Guide." This documentation is available as part of the VMware VI3 SDK or individually (with the exception of the Reference Guide).

In this article, I will discuss the two of the SDK's concepts that one must understand to write even the most basic code, and I will attempt to relate new concepts to familiar ones in order to make them easier to understand. The first section will discuss the SDK's two object types, managed objects and data objects. The second section will cover the VI3 hierarchy and structure.

The second part of the article talks about what version of .NET to use, how to generate client-side code and demonstrate a simple, real-world program written in C# that interacts with the VI3 SDK.

And part three of the article describes how to alter your VI3 configuration with the VI3 SDK and C#.

Read Part 1

Read Part 2

Read Part 3