In our last post we saw how to use the enumeration endpoint to search for particular objects. In this post we take that knowledge to get ILM’s schema. Since ILM’s schema is dynamic and customizable, you must enumerate the ILM objects related to schema. There is no static XSD to reference. The three objects of note:
Please note that the code posted below is slightly changed from the code posted on MSDN Code Gallery. The key difference is we output the schema to a file instead of printing it to the console. I realized that reading the console was less than ideal given the large number of ILM objects and attributes. I uploaded my copy of the output on the MSDN Code Gallery downloads page since I know copying code from blogs can be cumbersome. This is the schema in ILM “2” RC, and to be honest, I use it as a reference during the week.
The following code should look familiar from last post since it merely uses the enumeration client and combines the output in a useful way.
Let’ s go over the code:
That’s it! You now know how to combine data from ILM enumerations into something that’s useful for you and your customers.
Final note about the sample client: internally we treat all data as strings so the data type doesn’t have a direct impact on you explorations. However, please note that the server enforces data types on all values sent. These failures result in invalid representation faults.