The type 'x' is defined in an assembly that is not referenced. You must add a reference to assembly 'abc123'.

I have a .NET 2.0 web application that references my assembly 'abc123'. The assembly exists in the GAC and I've verified that it is the correct(same) version. The rest of application has no issues except for one .aspx page. The page in question has a repeater that displays a user control as one of its "fields". Upon binding a list of type y to the repeater I pass the user control a list of type x (a property of y) as shown here:

<uc1:usercontrol id="ucusercontrol " runat="server" myPublicUserControlProperty='<%#Eval("CollectionOfX") %>'/>

On the user control's property set, I bind the list of type x to a gridview in the user control.

One strange thing to note is that this report works fine on my development pc but not on any servers once I deploy. My pc is Windows XP, IIS6, VS2005. The servers are Windows Server 2003, IIS6.

I hope I explained that well enough. Thanks in advance for any insight you can provide.

+1  A: 

When troubleshooting these types of problems, the Fusion Log Viewer has always been a great help.

+5  A: 

I'm Mike's coworker, and we worked out a solution.

The type X is defined in his assembly, that is only in the GAC. Even though his ASP.NET web appplication did have a reference, it was failing to load from the GAC only for this UserControl. The rest of the application worked as expected. We confirmed the failed loading by placing a copy of the assembly in the bin directory, and everything worked. We removed the assembly, and the problem came back.

Our solution was to manually add an entry to the web.config in the assemblies section to point ASP.NET to the GAC.

It looks like any time you reference a type in the page (not the code-behind), you need the assembly information defined in the web.config file or in a page directive.

        <add assembly="MyAssembly, Version=, Culture=neutral, PublicKeyToken=[MyPublicKeyToken]"/>   
Aaron Daniels

There's also a bug that can manifest itself with similar symptoms, described here.

The workaround is to delete everything in the C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\ directory, and it only seems to manifest itself in debug mode.