I have been directed by my team lead to remove a dll I am responsible for
from the bin directory of our ASP.NET 2.0 web application by changing the
CopyLocal property to False. I have done this and am getting the following
error:

Could not load file or assembly 'GrangeAJAXComponents' or one of its
dependencies. The system cannot find the file specified.

I have installed GrangeAJAXComponents.dll into the GAC and verified its
version and public key. I have opened the project file in Notepad and
verified that the version number and public key match what is displayed in
the GAC:

 <Reference Include="GrangeAJAXComponents, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=82f335bc3105596d, processorArchitecture=MSIL">
   
<HintPath>C:\Blocks\GrangeAJAXComponents\GrangeAJAXComponents.dll</HintPath>
 </Reference>

The Assembly Binging Log from Fusion shows the following:

The operation failed.
Bind result: hr = 0x80070002. The system cannot find the file specified.
<snip>
LOG: DisplayName = GrangeAJAXComponents
(Partial)
<snip>
LOG: Policy not being applied to reference at this time (private, custom,
partial, or location-based assembly bind).
<snip>
LOG: All probing URLs attempted and failed.

By contrast, another dll which is referenced in precisely the same way has
the following log:

The operation was successful.
Bind result: hr = 0x0. The operation completed successfully.
<snip>
LOG: DisplayName = WebCustomValidationControls, Version=2.0.0.1,
Culture=neutral, PublicKeyToken=ed0771a7483cd66d
(Fully-specified)
<snip>
LOG: Post-policy reference: WebCustomValidationControls, Version=2.0.0.1,
Culture=neutral, PublicKeyToken=ed0771a7483cd66d
LOG: Found assembly by looking in the GAC.
LOG: Binding succeeds. Returns assembly from
C:\WINDOWS\assembly\GAC_MSIL\WebCustomValidationControls\2.0.0.1__ed0771a7483cd66d\WebCustomValidationControls.dll.
LOG: Assembly is loaded in default load context.

Obviously the problem is that GrangeAJAXComponents is using a partial
binding, but for the life of me i cannot figure out why. Everything about the
way the two dll's are referenced seems to be the same. I've triple-checked
everything and don't know what to try next. Any ideas would be greatly
appreciated.