graye,
Thanks for the response. The mof file is inserting a new WMI Class which has its own methods and properties. I will not be using a pre-existing class and this will become it's own provider. I am using the Management classes to interact and have no problems with that. Here is an example of what I have done.
- used mofcomp to compile mof file
- user regsvr32 to register dll file
Are there any steps that I need to take in order to get this to work. Once I compile the MOF I can connect to that class, but when I execute the method it tells me that the "Provider load failure" error. I then run regsvr32 and sometimes I get the provider error and sometimes I get "Provider is not capable of this operation" or something of that nature, don't remeber the exact error off the top of my head. From my understanding this is all that I should have to do unless I am missing a step.
Thanks for the help.
Jason
Main Topics
Browse All Topics
by: grayePosted on 2006-08-03 at 08:48:05ID: 17242730
Is your DLL going to be a "consumer" of an existing WMI class? For example is it going to be pulling information from the Win32_Processor class?
...or is your DLL going to be a "provider" where you'd be creating a new WMI class (not one of the standard WMI classes)
99.44% of the time, an application (either an EXE or a DLL) would be just consuming a WMI class. This wouldn't require you to do compile a MOF file or any of that. Instead you'd just use the .Net Frameworks System.Management classes to interact with WMI.