Eric,

>I was assuming that all I had to do was add the class project as a reference in the windows project and .NET would be smart enough to sort out it's location. <

Yes, that should be all you have to do. Have you tried removing the reference and adding it back in?

~~Bonnie





>Gmapper doesn't need to go in the GAC in fact that would be an undesirable situation since I'm in development. All I'm really trying to do is have a solution with a class project and one windows form to test it. The Gmapper class does nothing at this point except return "Hello World". I was assuming that all I had to do was add the class project as a reference in the windows project and .NET would be smart enough to sort out it's location. What is frustrating is the code window's intellisence sees it, and the class browser sees it. The compiled form throws up as soon as it sees Gmapper Gmapper1 = new Gmapper();. The code window has no problem with this line nor does the compiler. Like I said I've tried adding a reference to the DLL every way possible in .NET and I get the same error.
>
>
>>Eric,
>>
>>Don't know why you're having so much problem with this. It's typically pretty much straightforward. A question on your Gmapper DLL ... does it NEED to go in the GAC? I'm wondering if that's where your problem lies? Try to avoid if that possible.
>>
>>~~Bonnie
>>
>>
>>
>>>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.