Currently it is assumed that `nvml.dll` is located in
```
%ProgramW6432%\NVIDIA Corporation\NVSMI\nvml.dll
```
Not everyone has it installed there. Those that have the nvidia drivers
installed through windows updates will have it in in
`%WINDIR%\system32\nvml.dll` and won't have anything under the "NVSMI"
directory.
Instead of hard coding `%WINDIR%\system32\nvml.dll` as a search
location, we can load whatever `nvml.dll` appears first in the search
order:
```csharp
LoadLibrary("nvml.dll")
```
From [Standard Search Order for Desktop
Applications](https://docs.microsoft.com/en-us/windows/win32/dlls/dynamic-link-library-search-order#standard-search-order-for-desktop-applications):
> 1. The directory from which the application loaded.
> 1. The system directory. Use the GetSystemDirectory function to get the path of this directory.
> 1. The 16-bit system directory. There is no function that obtains the path of this directory, but it is searched.
> 1. The Windows directory. Use the GetWindowsDirectory function to get the path of this directory.
> 1. The current directory.
> 1. The directories that are listed in the PATH environment variable. Note that this does not include the per-application path specified by the App Paths registry key. The App Paths key is not used when computing the DLL search path.
`%WINDIR%\system32` is the system directory and thus `nvml.dll` is loaded.
This will also allow those interested to override the `nvml.dll` by
placing their own in the current directory as LibreHM without effecting
a system installation.
Only if there is no `nvml.dll` in the search space does LibreHM fallback
to searching program files. This may technically be a breaking change
for those that have `nvml.dll` in both the search space (like
`%WINDIR%\system32\nvml.dll`) and `%ProgramW6432%\NVIDIA
Corporation\NVSMI\nvml.dll` and those files differ. I don't suspect this
to be a common occurrence.
If this is expected to be a common occurrence I can switch the logic such
that program files is checked before the standard search space, though
this would make it so one couldn't override the program files
`nvml.dll`.
Tested it and works great so far!
* Added basic Nvidia NVML library support and power usage sensor
* Added basic Nvidia NVML library support and power usage sensor
* Added Initialised check
* Made NvmlDevice internal
* Code formatting
* Move NvmlDevice and NvmlReturn to separate files
* Move code from NvidiaNVMLGPU class to NvidiaGPU class
* Replace call to SetDllDirectory with LoadLibrary/FreeLibrary and code formatting changes
* Made native methods private
* Fixed p/invoke definitions, removed unnecessary try/catch blocks. Code style cleanup
* Hardware in IGroup is now IEnumerable. No point to call ToArray each time.
* Use ValueTuple insead of custom pair.
* ListSet -> HashSet
* Ring Collection -> List
* ReadOnlyArray -> ReadOnlyList
System.EntryPointNotFoundException: Não é possível localizar um ponto de entrada denominado 'nvapi_QueryInterface' na DLL 'nvapi.dll'.
em PInvokeDelegateFactoryInternalWrapperType38.nvapi_QueryInterface(UInt32 id)
em OpenHardwareMonitor.Hardware.Nvidia.NVAPI.GetDelegate[T](UInt32 id, T& newDelegate)
em OpenHardwareMonitor.Hardware.Nvidia.NVAPI..cctor()
System.NullReferenceException:
in OpenHardwareMonitor.Hardware.Nvidia.NvidiaGroup..ctor()
in OpenHardwareMonitor.Hardware.Computer.Open()
in OpenHardwareMonitor.GUI.MainForm..ctor()
in OpenHardwareMonitor.Program.Main()
Nick Babcock