ASP.NET Framework never forgets a reference?

[Eidolon]

I have an application which had references at one point to the
CrystalDecisions.Shared... libraries. We have since removed those
references. A search on all binary and text files in the project
directory (&recursive) reveals not a single file which contains a
reference to Crystal anymore.
However, if i go into the
"\\myserver\c$\winnt\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET
Files\my_webapp\...\assembly\dl2" folder (where my_webapp is the name of
our application), along with our current references, it still puts
folders in there for the crystal ones too. I've even tried deleting the
"\Temporary ASP.NET Files\my_webapp" folder, and letting the server
recreate it. Still those crystal DLLs come back, even though we have not
one reference to them ANYWHERE in our project or code files.
Can anyone explain why this is?

Cheerz!

 

[Michael Per]

Check your web.config. Sometimes the DLL names make their way there...

 

[Eidolon]

Check your web.config. Sometimes the DLL names make their way there...

I just looked there and did not see it anywhere. It would be in a
<compilation\assemblies\add> key? We have one DLL in there, but its one
we put in deliberately which has no connection to crystal.