have created a custom event class to log when a record of any type is deleted by an administrator through the site's administrative area. To make thecustom events to be dynamically loaded correctly when the application starts,iplaced themin their own pre-compiled assembly I then referenced the compiled dll for that class to the solution,hence having the dll in the bin directory. The reason for using a custom base class is soi can add a rule to the web.config file's <health Monitoring> section to log all events that inherit from this WebCustomEvent class, instead of registering them all individually The application runs and functions well on my development computer, however on deploying to the DASP server as a precompiled application i get problems. I have made sure that the dll exists andthat it is incorrect form in my bin directory. Could someone please help out?. The following is the error that i get Configuration Error Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately. Parser Error Message: Could not load file or assembly 'C24CustomEvents' or one of its dependencies. The system cannot find the file specified. Source Error: Code: Line 54: </providers> Line 55: <eventMappings> Line 56: <add name="C24 Events" type="Oscar.Channel24.WebCustomEvent, C24CustomEvents"/> Line 57: </eventMappings> Line 58: <rules> Source File: E:\web\channel24n4\htdocs\web.config Line: 56 Assembly Load Trace: The following information can be helpful to determine why the assembly 'C24CustomEvents' could not be loaded. Code: 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].
This error is definitely caused by a missing dll in your application root's bin directory. Check the bin directory and make sure the dll is there. Bruce DiscountASP.NET www.DiscountASP.NET