Assembly Binding Log Viewer (Fuslogvw.exe)

Assembly Binding Log Viewer (Fuslogvw.exe)

The Assembly Binding Log Viewer displays detailed information about the failed assembly bindings. This information helps you diagnose why the. NET Framework cannot find an assembly at run time. These failures are usually caused by an assembly deployment to the wrong location or a version number or culture mismatch. If the common language runtime fails to find an assembly, it typically behaves as typeloadexception in your application. using assembly Binding Log Viewer

Use the assembly binding log Viewer to perform the following actions: View the contents of an assembly binding log. Change the view of the log location. View detailed information about a specific failure. Deletes an item from the log. Deletes all items from the log. Refreshes the user interface. Exit the browser.

You can set the registry key so that additional information is displayed in the viewer: All bindings are recorded in the log. Failed to record binding to satellite assembly.

View the contents of an assembly binding log to run Fuslogvw.exe from the command line.

The following screenshot shows the assembly Binding log viewer.

assembly Binding Log Contents

The viewer will display an entry for each failed assembly binding. For each failure, the viewer describes the application that started the binding, the Assembly to which it is bound (including name, version, culture, and public key), and the date and time of the failure.

Change the Log location view Select the Default option button to view binding failures for all application types except asp.net. By default, log entries are stored in WinInet cached user directories on disk. Select the asp.net option button to see that the ASP.net application's bindings failed. It is not appropriate for ASP.net to store log entries based on the user because in a WEB server scenario all users typically run with the same user ID. Therefore, ASP.net fails to record its bindings in each application cache directory. Select the Custom option button to view the binding failure information in the customized directory that you specify. You must specify a custom location where you want the runtime to store these logs by setting the registry key Hklm/software/microsoft/fusion/logpath to a valid directory name. This directory should be clean and contain only the files generated by the runtime. If the directory contains an executable that generates a failure that can be logged, the failure will not be logged because the tool attempts to create a directory with the same name as the executable file. In addition, an attempt to run an executable file from a log location also fails. Note The default binding location is better than the custom binding location. The runtime stores the default binding location in the WinInet cache, so that the location can be automatically cleared. If you specify a custom binding location, you need to clear it yourself.

View details about a specific failure the application name of the item you want to select in the viewer. Click the View Log button. Alternatively, you can double-click the selected item.

The tool displays the following details about the selected binding failure: Specific reasons for the binding failure, such as "File not Found" or "version mismatch." Information about the application that started the binding, including its name, the root directory of the application (AppBase), and a description of the private search path, if one has such a path. The identity of the Assembly that the tool is looking for. A description of any application, publisher, or administrator version policy that has been applied. Whether the assembly has been found in the global assembly cache. A list of all the URLs being probed.

Assembly Binder Log Entry (3/5/2002 @ 12:54:20 PM) * * * operation failed. Bind result:hr = 0x80070002.

The system cannot find the file specified. Assembly Manager loaded From:c:/winnt/microsoft.net/framework/v1.0.3705/fusion.dll Running under executable c:/ Program files/microsoft.net/frameworksdk/samples/tutorials/resourcesandlocalization/graphic/cs/ 

Graphicfailtest.exe---A detailed error log follows. = = = Pre-bind state information = = Log:displayname = Graphicfailtest.resources, version=0.0.0.0, culture=en-us, PublicKe Ytoken=null (fully-specified) log:appbase = C:/Program files/microsoft.net/frameworksdk/samples/tutorials/ Resourcesandlocalization/graphic/cs/log:initial privatepath = null Log:dynamic base = NULL Log:cache base = NULL LOG:
AppName = NULL Calling Assembly:graphicfailtest, version=0.0.0.0, Culture=neutral, Publickeytoken=null.
= = = Log:processing DEVPATH. Log:devpath is not set.
Falling through to regular bind. Log:policy not being applied toReference at this time (private, custom, partial, or location-based assembly bind). Log:post-policy reference:graphicfailtest.resources, version=0.0.0.0, culture=en-us, Publickeytoken=null LOG: Attempting download of new URL File:///C:/Program files/microsoft.net/frameworksdk/samples/tutorials/
Resourcesandlocalization/graphic/cs/en-us/graphicfailtest.resources.dll. log:attempting download of new URL File:///C:/Program files/microsoft.net/frameworksdk/samples/tutorials/
Resourcesandlocalization/graphic/cs/en-us/graphicfailtest.resources/graphicfailtest.resources.dll. log:attempting download of new URL File:///C:/Program files/microsoft.net/frameworksdk/samples/tutorials/
Resourcesandlocalization/graphic/cs/en-us/graphicfailtest.resources.exe. log:attempting download of new URL File:///C:/Program files/microsoft.net/frameworksdk/samples/tutorials/
Resourcesandlocalization/graphic/cs/en-us/graphicfailtest.resources/graphicfailtest.resources.exe. Log:all probing URLs attempted and faileD. 

remove a single item from the log Select an item in the viewer. Click the Delete Entry button.

Remove all items from the log Click the Delete All button.

Refresh the user interface click the Refresh button. The viewer does not automatically detect new log entries while it is running. You must use the "Refresh" button to display them.

exit the browser and click the Exit button. Additional configuration Settings

logging all bindings in the viewer sets the Hklm/software/microsoft/fusion/forcelog registry value to 1(the value is DWORD).

By default, Fuslogvw.exe only attempts to record a failed location assembly. You may experience situations where you need to see all of the successful assembly bindings. For example, you might want to verify that the assembly is loading from your application directory, rather than from the global assembly cache. Set this registry key to force Fuslogvw.exe to record all assembly bindings.

record binding to satellite assemblies failed to set the Hklm/software/microsoft/fusion/logresourcebinds registry value to 1(this value is DWORD).

By default, Fuslogvw.exe does not record attempts to locate satellite assemblies that failed. Setting this registry key enables this feature. Please see

. NET Framework Tools | Global Assembly Cache | How the Runtime Locates Assemblies | TypeLoadException class