CS Tidbits #10: Troubleshooting Assembly Binding Failures

This is probably the number 1 source of headaches for new Community Server installations, a runtime exception stating something similar to “Couldn’t load <foo> assembly” or whatnot.  Folks new to .Net, or system administrators who may not be intricately familiar with the bevy of tools that ship with the .Net framework don’t realize that the framework ships with a GUI tool that can aid in diagnosing why CS can’t load a specific assembly:  The Assembly Binding Log Viewer (NOTE: the article states that you need to run this from a command line…it’s actually the .Net Command Prompt that you need to execute fuslogvw.exe from).  I’ll let the article speak for itself, but this tool is invaluable for figuring out issues with assembly load failures.

Share this post: | | | | |

Only published comments... May 30 2006, 03:47 PM by Jayson Knight

Filed under: .Net, CS Tidbits

About Jayson Knight

Jayson Knight was clueless to the computer programming world until he took a C++ class in college. The rest is proverbial history. He has been building applications targeting the .Net framework for 7 years, focusing mainly on internet technologies and database driven web application development.

Most recently he left the world of Corporate IT to finish up his degree in Chemistry, with an eye on Medical School and an Anesthesiology residency program. Read this post for more information.

He is also a Community Server MVP: Community Server is the software that runs this site, plus many others on the web. For more information, check out http://csmvps.com.

When he finds time to pry himself away from his computer and university studies, he can be found on the mountain bike trails when it's warm, and on the ski slopes when it's cold.