Click here to Skip to main content
15,071,800 members

Comments by Heath Stewart (Top 5 by date)

Heath Stewart 18-Mar-12 23:52pm View
   
It has nothing to do with "power". It's a matter of what is exposed for the API to call, or how much information you store within your own program you write in any language. Changes are that this cpu-id probably has data on a lot of different motherboard manufacturers, and what they can glean from low-level calls along with that data provides an answer. The WMI provider implementation apparently didn't go to that length.

You can search the Internet and read up on detecting DDR2 yourselves. All sources I've found say it's not standard.
Heath Stewart 14-Jul-11 19:31pm View
   
That wasn't mentioned in your original question. If that is the case, then that version of the ADODB assembly is probably no longer installed or deprecated. For whichever project is failing, add a reference and look for ADODB in the assembly list. Also, during the conversion the wizard shouldn't raised any warnings or errors. If those reports are still available, you should review it for any prescribed fixes.

In general, you might consider moving to ADO.NET instead of ADO. The concepts are similar but there's more power and abstraction in ADO.NET. I would imagine that the conversion report would direct you to more information about how to do that.
Heath Stewart 14-Jul-11 14:07pm View
   
Unforutnately, it all depends on what motherboards support and how they expose the information. Seems rather unfortunate it's not standardized given what WMI (or CMI in general) is for.
Heath Stewart 12-Jul-11 18:24pm View
   
I wouldn't mess with the users' folders. That could result in changes to their Exchange account or any other primary account. Instead, you could also use a search folder with global scope and a search filter like so: NOT emailaddresses:=[]
Heath Stewart 10-Jul-11 23:02pm View
   
Deleted
The name has nothing to do with it. The return type of GetData() is important. If it just returns base types like Object or IEnumerable<Object>, etc., then the type is just that - a base type. IntelliSense won't give you much then. But if the declared return type of GetData() is more specific then var will be more useful.

Of course, if you just return something of a base type and - without casting - assign to a derivative type you won't be able to compile it, and even if you cast all objects returned by GetData() better cast correctly.