April 2002
Intermediate to advanced
1024 pages
23h 26m
English
Content preview from .NET Common Language Runtime UnleashedBecome an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
Start your free trial
Determining Assembly Load Failures
With managed code and the CLR, an assembly might not load properly. This usually is the result of an assembly being in the incorrect location or having been renamed, or because of a version or culture mismatch. For whatever reason, it can be annoying when the application will not run because of this error. It is often difficult to trace down the cause of this error. (Compare this to the old problem that was encountered when a DLL could not be found.) A tool called the Assembly Binding Log Viewer (fuslogvw.exe) can help diagnose a problem when an assembly does not load correctly.
In Chapter 14, you saw an application called ThreadPoolTest.exe that created an AppDomain, loaded an Assembly into that AppDomain