File Not Found – Assembly Binding Error


I am sure many of you might have come across the “File Not Found” error related to the Assembly Binding.


FileNotFound Error


The best way to diagnose is to use the Fusion Log Assembly Viewer. The tool FUSLOGVW.exe is located at C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin

You can also access this tool from your Visual Studio Command Prompt.


Fusion Assembly Log Viewer Settings:

FusLogVw Settings

  • Set your Log Settings as per the screenshot above. Set your own custom log path.
  • Close the Fusion Assembly Log Viewer
  • Once you are done with those settings make sure you delete all the Temporary ASP.NET Files from the “Windows\Microsoft.NET\Framework\v2.0.50727” folder.
  • Do an IISRESET
  • Start the Fusion Assembly Log Viewer
  • Open your ASP.Net web application and recreate the erroring scenario.
  • Click Refresh button in the Log Viewer
  • Look for App_Web_error.aspx entry..and move up in the list you will find the dlls that the application is trying to bind. Double click it and you will find the details of the binding error.

FusionLog Error Output



Unable to Open a CHM file – You get a Unable to display web page error

When you try to open CHM files you might encounter issues. This is primarily due to 2 reasons.


  1. Security
  2. File path contains certain characters like #, ?, &, +


To overcome the security issue you have to follow the steps below..

  1. When you open the file you will be prompted with a security warning which you can dismiss by un checking the “Always ask…” checkbox and clicking “Open” button.
  2. Right Click the file and select properties from context menu. Click unblock button at the bottom and click Apply, OK




If you still get the error “This program cannot display the webpage” then verify if the path to the file has any invalid characters. For example a  path “C:\My C# Project Documentation\MyHelpFile.chm” will not work !


Change your path to “C:\My CSharp Project Documentation\MyHelpFile.chm” and it will work.

Error when trying to delete a master page, page layout from SharePoint master pages gallery


You might receive an error “This item cannot be deleted because it is still referenced by other pages”. I was searching through the web for a solution then I came across this site. This site gives you a neat little hack !


Reproducing the text from the original site.

Today I ran into an error while creating page layouts using a feature. I made a mistake in the XML that provisions the files to install with the feature for my page layouts. My problem was an incorrect value in the attribute for the content type ID linked to my installed page layout.

After realizing my mistake and correcting it, uninstalling the feature and reinstalling it again the original incorrect page layout was still installed. This seems to be normal in SharePoint. Even when deactivating and uninstalling a page layouts feature these pages still stay in the "Master Page and Page Layout Gallery". I still have to find the right documentation on why this happens but I imagine it has to do with ghosting of the pages.

Now back to my problem. Since the incorrect page layout was still installed and giving me error messages I tried to delete it manually from the gallery. This gave me the following error message:

"This item cannot be deleted because it is still referenced by other pages"

Even if this is not the case (there was no page using this page layout), the problem is mentioned in the following KB article:

The KB proposes to change the properties of the master page to Hidden. This workaround did not solve my problem since everytime I tried to access the page layout’s Properties screen I got another error message due to my mistake discussed above.

There was however one workaround that solved the problem:

  1. Create a new sub-folder in the master page gallery
  2. Move the page layout to the new folder (I did this by using SharePoint Designer)
  3. In the MOSS interface, delete the complete folder by using the dropdown menu.

Yep, my page layout is finally gone from the gallery!

While my problem was specific to a page layout I think the same solution will work with master pages as well.

Hello world!

Welcome to . Through this blog I would like to share my experience in the world of programming. Also I might stray into some generic topics that interests me 🙂