WMI root entry OpenHardwareMonitor don't removed.

[T-Troll]

How it works now:

• Then started, OHM create WMI namespace and classes to provide data
• Even if not active or removed, namespace still into WMI.

What i asking for:

• Remove WMI namespace then data is not available (at application quit).

[pgrawehr]

Which version are you using? The latest version does not use WMI at all any more (but a webservice instead)

[T-Troll]

Yes, i check the old one....

It's hard to hear you remove WMI support - it widely used by many 3rd-party applications, including mine AlienFX-Tools. So we stuck at base OHM version....

Is it any way to return it back?

[pgrawehr]

I don't think so. It was just unreliable. Often, without any visible reason, the sensors where not available on WMI, and then you reinstalled the application (or rebuilt it, or did some other no-change update) it worked again. It's probably better if you update your client code. There's a C# client available as part of the Iot.Device.Bindings package (from https://github.com/dotnet/iot). It uses just a simple web request with a json reply, which should also be fairly straight forward in C++.

[T-Troll]

Ok, i got your point.

But, anyway, you broke all 3rd-party Windows apps and scripts who use it.

Please close this issue if returning WMI back is not an option.

[pgrawehr]

I can consider it, but I mostly made that change for our own use case, where the existing WMI solution just didn't work reliably. Of course, I do not know how many libraries and scripts use the WMI interface.

[alexxxdev]

webservice does not replace WMI in any way ((

[T-Troll]

@alexxxdev It's play against Occam's razor in many cases as well. PS: I see some guys even port WMI to Linux to use some proprietary ACPI methods. Keyword: Clevo.

[pgrawehr]

webservice does not replace WMI in any way ((

Why not? It's much more flexible and system independent.

IIRC one of the reasons for removal was that .Net6.0 no longer supports the WMI api, at least not in the way it was used before.

[T-Troll]

Why not? It's much more flexible and system independent.

Patrick, do you remember about Linux way? Don't try to be universal, try to do small task good! WMI is a Windows way to do so.

.Net6.0 no longer supports the WMI api

.Net for portability? Hmmm... Looks strange. I check it, yes, seems like Microsoft.Management.Infrastructure is obsolete. Bad news for c# coders, seems like MS fade it away.

[pgrawehr]

I am not the guy that always wants to be universal. But if the universal solution is the easiest, and the existing, non-universal solution is deprecated, there's no reason to try to write some hack to stick with the old way.

[T-Troll]

Patrick, thank you for your comments! I switch to Libre OHM clone, they still support WMI.

I close this issue.

[alexxxdev]

I switch to Libre OHM clone, they still support WMI.

thx, I will also try to use this