Hi Larry,

The problem you are experiencing is that everytime you recompile your dll in the GAC, a new version is created. If you were to recompile with the same version, then the new code would run (however I wouldn't recommend this). You can use publisher policy or configuration files for the client apps to redirect the version they bind to. Here is an article that explains how to work with versioning in your applications to get the behavior you want:

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

>Are .dll files compiled into the web service program?
>
>If I make a change to an object file (.dll) and install it in the GAC, the client program does not know about the change. I've found that if I recompile the client, *then* it will recognize the new behaviours in the .dll...
>
>Am I mistaken in believing the following:
>
>- I can build a business object into a .dll file and install it in the GAC
>- I can build client programs to access this business object remotely on a LAN, WAN, internet, whatever.
>- I can change the logic in the business object and re-install a new .dll in the GAC
>- All the client programs will behave according to the new business object's logic
>
>Is the .dll compiled into the client? It seems to be, regardless of the setting of "Copy local"...
>
>Now, I'm asking this question for a third party, so I'm fuzzy about the details, but I too am confused about his findings...
>
>TIA