>>It might be an indication that it is being compiled/loaded. That doesn't mean it will be used. You really need to get positve proof that the method is being called.
>
>All Web sites I have has the Web.Config file in the root directory. The Web site wouldn't be able to work if I wouldn't have that file in there.
>
>Here is what I have in it:
>
>

><?xml version="1.0"?>
><configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">
>	<appSettings/>
>	<connectionStrings/>
>	<system.web>
>		<identity impersonate="true"/>
>		<compilation debug="false" targetFramework="4.0">
>			<assemblies>
>				<add assembly="System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
>				<add assembly="System.Management, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/></assemblies>
>		</compilation>
>		<authentication mode="Windows"/>
>		<customErrors mode="Off"/>
>		<pages validateRequest="false" enableViewStateMac="false" enableEventValidation="false" controlRenderingCompatibilityVersion="3.5" clientIDMode="AutoID">
>		</pages>
>		<httpRuntime executionTimeout="300" maxRequestLength="10000" requestValidationMode="2.0" requestValidationType="Framework.Framework.CustomRequestValidation,Framework"/>
></system.web>
>
></configuration>
>

Looks right.
Not sure whether it would make a difference but I see that although you are targeting ASP.NET 4 you have the requestValidationMode="2".
The documentation isn't very clear but it seems that when set to '2' validation is only applied to pages (and even then can be suppressed on individual pages). You could try removing that attrib (or setting it to "4")
But (and I keep coming back to this) you really must determine whether the method is simply not being called or whether it is being called but not behaving as expected. Set a break point, throw an exception, write to the event log, whatever.......