An interesting note is that if I reference the original assembly on the client, then everything works fine. However, we do not wish to distribute the implementation assemblies to the client. The deployment will be a physical three tier scenario. Only a metadata assembly is appropriate for security reasons.
The SoapSuds utility main purpose is for creating proxies for web services. As such, I found that it doesn't work too well for tcp channels. Usually there will be some methods not included in the resulting assembly. The stubbed out copy of the assembly for creating metadata only assembly works fine, but I don't understand why it is having these problems with enumerations.
