WRN: Asssembly binding logging is turned OFF






3.67/5 (3 votes)
The resolution of warning which does not let you add your custom control
--------------------------- Microsoft Visual Studio --------------------------- Failed to create component 'CustomControl'. The error message follows: 'System.IO.FileNotFoundException: Could not load file or assembly 'WinsssCtrls, Version=1.0.1.0, Culture=neutral, PublicKeyToken=9b172c8695ba0f39' or one of its dependencies. The system cannot find the file specified. File name: 'WinsssCtrls, Version=1.0.1.0, Culture=neutral, PublicKeyToken=9b172c8695ba0f39' at WnCols.rlLogIn.InitializeComponent() at WnCols.rlLogIn..ctor() in D:\Folder\Mine\VSWork\Source\WCtrls\WiCols\trlLogIn.cs:line 20 WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]Today I came to get this warning and to my utmost dismay, I could not add my custom controls to another project. After digging it out, I could not get enough information. Therefore, I thought of sharing it with all. The project hierarchy is like: I have a library which contains wrapper windows controls, another library utilizes these wrapper controls and this library contains custom user controls. Then I have the main project which utilizes these custom user controls. While adding the custom user control, I got the above warning and could not load the custom user controls. To resolve the issue, I recompiled my library containing wrapper windows controls and added its reference to my custom user controls. I recompiled my custom user control library and added its reference to my main project. After that, all went fine. Hope this may save some of your time. Happy coding! :)