.NET assembly loading is a complex topic, but it doesn't have to be. If you use unsigned and local assemblies it works nearly seamlessly. If you sign your assemblies it get way more complicated as versioning kicks in and you need to make sure that hte application loads the correct version. If you're developing with DLLs deployed to the GAC it gets very difficult to do this, which is one reason I avoid the GAC like the plague if i can avoid it.
The thing to make sure of is to remove all assemblies from the project in question and then add everything back in as related project references. It sounds like you may have a stale copy in one of those satellite projects.
Also for development I'd advise to not set up versioning. Leave that as a final step before deploying or not at all if your application is a one shot all in one place install.
+++ Rick ---
>No matter what I do I get this error when trying to test a DLL project in a winform project.
>
>
>An unhandled exception of type 'System.IO.FileNotFoundException' occurred in WindowsApplication1.exe
>
>Additional information: File or assembly name Gmapper, or one of its dependencies, was not found.
>
>
>There are no compiler errors and intellisence can clearly see the DLL after I add the DLL reference to the winform application project and add code to create instances of Gmapper. However I get the above error even if I copy the DLL into every possible location in the file system.
>
>Also, why doesn't .net show my assembly in the list on the .NET tab of the Add Reference dialogue window after I add my DLL to the GAC using gacutil.exe? This whole issue should be a no brainer yet it is ambiguous at best to understand how .NET handles DLLs. It is especially dumb founding when the DLL in question is part of the same solution as the form's project.
>
>Finally, why is this such a hassle? It seems to me that adding the DLL's class project as a reference in the winforms project should supply enough information to begin testing code yet I'm spending hours plodding through unclear documentation and Google links.
