<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Writing WMI provider in a day</title><link>http://blogs.msdn.com/wmi/archive/2009/06/19/writing-wmi-provider-in-a-day.aspx</link><description>Writing WMI provider in native code has steep learning curve. It involves writing MOF files and implementing methods from IWbemServices and IWbemProviderInit interfaces. Sometimes it becomes difficult and time consuming to debug issues in the WMI provider.</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Writing WMI provider in a day</title><link>http://blogs.msdn.com/wmi/archive/2009/06/19/writing-wmi-provider-in-a-day.aspx#9825059</link><pubDate>Thu, 09 Jul 2009 02:16:37 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9825059</guid><dc:creator>a dev</dc:creator><description>&lt;p&gt;debugging this is a nightmare. WMI is poorly designed when it comes to debugging wmi providers.&lt;/p&gt;</description></item><item><title>re: Writing WMI provider in a day</title><link>http://blogs.msdn.com/wmi/archive/2009/06/19/writing-wmi-provider-in-a-day.aspx#9847000</link><pubDate>Fri, 24 Jul 2009 03:49:42 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9847000</guid><dc:creator>kmathur</dc:creator><description>&lt;p&gt;Do let us know if you have any suggestions to improve the debugging experience. &lt;/p&gt;
</description></item><item><title>re: Writing WMI provider in a day</title><link>http://blogs.msdn.com/wmi/archive/2009/06/19/writing-wmi-provider-in-a-day.aspx#9902552</link><pubDate>Fri, 02 Oct 2009 22:46:06 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9902552</guid><dc:creator>bm</dc:creator><description>&lt;p&gt;WMI provider using System.Management.Instrumentation (WmiConfiguration) sucks. Writing is simple, but testing to see if it works is hell of a deal.&lt;/p&gt;
&lt;p&gt;I wrote a simple windows forms application and with a WMI provider class (very basic with a key and two readonly properties), installed it using installutil and then published the instance of the class. Wbemtest wouldn't show any instances. No matter what i tried. &lt;/p&gt;
&lt;p&gt;However if I use Instrumented attribute and associated classes, it works.&lt;/p&gt;
&lt;p&gt;I can't figure out what is it that I am missing.&lt;/p&gt;
</description></item><item><title>re: Writing WMI provider in a day</title><link>http://blogs.msdn.com/wmi/archive/2009/06/19/writing-wmi-provider-in-a-day.aspx#9921336</link><pubDate>Thu, 12 Nov 2009 13:52:57 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9921336</guid><dc:creator>mabra</dc:creator><description>&lt;p&gt;Hi !&lt;/p&gt;
&lt;p&gt;Thanks for this pointer!&lt;/p&gt;
&lt;p&gt;But:This is a badly written article, because it starts very deep, giving you no chance to understand the code without first studying the SDK ... do I have to implement my own process, or not?? Ok, I am searching ...&lt;/p&gt;
&lt;p&gt;Although WMI is very important and generally a good thing, it is - facing it's complexity - a underdocumented thing. This moment, I was looking for all classes which are singletons:You have no hope with the SDK [no overviews/tables with details]. As alway, I stranded to write the next hack ....&lt;/p&gt;
&lt;p&gt;MS should really start to make some quality control [not only for the software, but for their articles also!] and finally implement the wmi properties, administrators are looking for [yes, the huge amount of NULL values, like fileCRC, stati - withound end!].&lt;/p&gt;
&lt;p&gt;And it looks like, MS is interested mostly to have a good layer for SMS/MOM and so important providers [compare windows xp to server 2003] are removed, which could admins a good help!&lt;/p&gt;
&lt;p&gt;Just my two cents. I am using WMI sinde the beginning.&lt;/p&gt;
&lt;p&gt;br--mabra&lt;/p&gt;
</description></item><item><title>re: Writing WMI provider in a day</title><link>http://blogs.msdn.com/wmi/archive/2009/06/19/writing-wmi-provider-in-a-day.aspx#9937742</link><pubDate>Wed, 16 Dec 2009 17:10:08 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9937742</guid><dc:creator>wayne</dc:creator><description>&lt;p&gt;the article and frankly all information around this topic is a disaster. there isn't any books on the subject which means you have to try make sense out of examples that are messy and miss out valuable information. there are no step by step guides only fragments of code which then are thrown together in make shift examples that cannot be followed or understood. the codeproject have the best examples but even they are not clear about elements to the technology that need to be understood to succeed &lt;/p&gt;
</description></item></channel></rss>