We pay for user submitted tutorials and articles that we publish. Anyone can send in a contributionLearn More
Every one of us, software developers, experienced situations where the .Net Framework could not locate an assembly and ended up facing the TypeLoadException. These failures usually happen due to an assembly deployed to the wrong location or a mismatch in version numbers or cultures. A quick way to check what went wrong is to open the module window (Visual Studio) during debugging but that may be sometimes impossible or inconvenient because:
Luckily, there is an assembly binding log viewer which displays information that helps us diagnose why the .NET Framework can not locate an assembly at run time. This tool is called Fuslogvw (short for Fusion Log Viewer) and can be launched from the Visual Studio Command Prompt. Go to Start->Microsoft Visual Studio 2005/2008->Visual Studio tools->Visual Studio Command prompt and type fuslogvw. This is what you get:
Although this tool is already installed with the .NET Framework, many developers don’t know about it, so I hope that this post will help spread the word about fuslogvw because it may become very helpful sometimes.
Tags :assemblyBindingdiagnosefusionfuslogvwlog viewerTypeLoadExceptionVisual Studio
Copyright © 2012 Dev102.com
Breeze : Designed by Amit Raz and Nitzan Kupererd