Developer Ramblings

This post is going to be about using simple object collectors to get a list of virtual machines on a given host. Now, there are a couple of ways to do this, namely using traversal objects, but for this post, we are going to keep it simple. We will get to the TraversalSpec object in some later posts, so we will revamp this code at that time. For now, I am going to focus on creating simple collector objects so we can us them as building blocks. Disclaimer: I know there are some flaws in the code below, mainly traversing... [Read More]

Why doesn’t Apple allow developers easy access to their platform? Well, that is what this post will be about. As Apple releases more hardware it seems as though they are becoming more and more closed when it comes to opening up their API to developers, or at least giving developers some choice in how they develop their applications). As a point of full disclosure, in my day job I am a software engineer/Systems Architect, mostly on the Windows Platform. I am not prejudice on any platform, in fact I have both Windows and Linux running, as well as deal with... [Read More]

While writing some VMWare SDK/Web Services howto posts as well as some production code in C# I recently ran into an issue where the vimService object was taking upwards for 3 minutes to instantiate. I figured that I might have messed up on adding the web service reference, so I re-added the web service reference to the project by select “Add Web Reference”, then when it asked for the WSDL location put in our ESX server location. ie. /sdk/vimService?wsdl">/sdk/vimService?wsdl">https://<server>/sdk/vimService?wsdl. Everything should be be good with this right? Wrong… Just by doing this the vimService takes forever to load. After some... [Read More]

So I am trying to put together some short tutorials about using VMWare ESX Web Service together with .NET. These tutorials  are meant to be specific and pointed for a single item. So, on with the first posting for the ESX web Service API. Before you dig into the the code below, this code references a Web Service proxy object called VMWareWS. You can create this by adding a web reference to your visual studio project with the following url “http://<your esx server>/sdk/vimService?wsdl”, then naming it VMWareWS.   VMWareWS.VimService _service = new VMWareTesting.VMWareWS.VimService(); _service.Url = @"https://your esx server/sdk"; [Read More]

I am prototyping some ESX integration and needed to add a reference to the ESX web service, but couldnt remember what the URL was. So…. if you need to access the ESX from a Visual Studio project, You will need to add a Web Service Reference, and point the URL to the following link https://<your host>/sdk/vimService?wsdl That will give you aproxy object that you can now work with. Watch for more ESX/.NET posts here shortly.