search

AlexanderStohr / open-hardware-monitor

Automatically exported from code.google.com/p/open-hardware-monitor
0 stars 0 forks source link

System.IO.FileNotFoundException: Could not load file or assembly 'Aga.Controls ... #50

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
The complete exception message

---

System.IO.FileNotFoundException: Could not load file or assembly
'Aga.Controls, Version=1.7.0.0, Culture=neutral,
PublicKeyToken=fcc90fbf924463a3' or one of its dependencies. The system
cannot find the file specified.
File name: 'Aga.Controls, Version=1.7.0.0, Culture=neutral,
PublicKeyToken=fcc90fbf924463a3'
   at OpenHardwareMonitor.GUI.MainForm..ctor()
   at OpenHardwareMonitor.Program.Main()

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value
[HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind
failure logging.
To turn this feature off, remove the registry value
[HKLM\Software\Microsoft\Fusion!EnableLog].

---

I could neither identify the source of this error nor reproduce it. Maybe
trying to run the Open Hardware Monitor with "assembly bind failure
logging" enabled as described in the exception could give more hints about
what is going wrong.

Original issue reported on code.google.com by moel.mich on 28 Apr 2010 at 9:32

GoogleCodeExporter commented 9 years ago 
One way to create the error message is by starting the Open Hardware Monitor 
directly
from the zip file without extracting it all the files first.

The Open Hardware Monitor should verify that the files 

Aga.Controls.dll (always)
WinRing0.dll (x86)
WinRing0.sys (x86)
WinRing0x64.dll (x64)
WinRing0x64.sys (x64)

can be found in the same directory as the OpenHardwareMonitor.exe. If a file is
missing the application should display an error message and terminate without
throwing an exception.

Original comment by moel.mich on 30 Apr 2010 at 7:16

GoogleCodeExporter commented 9 years ago 
Revision r134 seems to have fixed the problem, as no further crashes have been
reported with release version 0.1.33.

Original comment by moel.mich on 14 May 2010 at 10:34