Based on your information, it appears that your project is not using the DLL in the GAC. Make sure you don't have the DLL where your application solution is . Here is an article that discusses how the runtime determines which assemby to use.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconhowruntimelocatesassemblies.asp

>Cathi,
>
>Thx for the response. Larry was posting on my behalf until my account was cleared and activated.
>
>I am hoping you can point me to something I am missing as I expected the bavior you describe but alas did not get the desired result.
>
>1) I am hard coding the version number to remove versioning from being one of the problems.
>
>2) I have recompiled the dll with new/different functionality and re-installed it in the GAC (using same version) many times ( I always remove the previous version). The client only picks up the new/different behavior if I recompile the client. It is not automatic. I have Copy Local set to False of course.
>
>Now, I could use the config file and have the client point to a new DLL via new versioning (I will test the limitations of this shortly), but I prefer to simply recompile the dll and have the change automatically reflected in the client.
>
>If it makes any difference, the client in my case is actually a Web Service running on the same machine as the GAC that contains the dll in question.
>
>Thx in advance,
>
>Brian
>*Remember, no matter where you go, there you are*