The approach is generally reasonable, but I’m concerned about introducing a new dependency. We strive to keep the dependency footprint minimal to avoid potential conflicts with user applications that might reference a different version of the same package. While adding a dependency is acceptable when strictly necessary, it’s still something we try to avoid.

In this case, the benefit seems marginal: we’re addressing a rare scenario (Windows systems without wmic) by pulling in a third-party library. That feels excessive. I’d prefer a simpler solution that invokes a command-line tool directly, without adding any dependencies.

The approach is generally reasonable, but I’m concerned about introducing a new dependency. We strive to keep the dependency footprint minimal to avoid potential conflicts with user applications that might reference a different version of the same package. While adding a dependency is acceptable when strictly necessary, it’s still something we try to avoid.

In this case, the benefit seems marginal: we’re addressing a rare scenario (Windows systems without wmic) by pulling in a third-party library

I don't believe Windows still ships with WMIC by default, and in any case WMIC is deprecated and will likely be removed entirely in a future version of Windows.

That feels excessive. I’d prefer a simpler solution that invokes a command-line tool directly, without adding any dependencies.

Fair enough. Since Microsoft suggests using Powershell for WMI interaction I'll work on a detector that gets the information through Powershell and scrap the WmiLight related code.

I don't believe Windows still ships with WMIC by default, and in any case WMIC is deprecated and will likely be removed entirely in a future version of Windows.

I wasn't aware of it; thanks for the information. Could you please add a brief note about the current and future state of WMIC to the comments in WmicCpuDetector?

I don't believe Windows still ships with WMIC by default, and in any case WMIC is deprecated and will likely be removed entirely in a future version of Windows.

I wasn't aware of it; thanks for the information. Could you please add a brief note about the current and future state of WMIC to the comments in WmicCpuDetector?

I've added the note as remarks in the WmicCpuDetector xml doc comments.

It's probably better to move the check to the WmicCpuDetector to check if wmic exists before starting the process (same as checking if powershell exists). [Edit] Can't hurt to have both checks.