(...) > some type of implementation dll to run against. an > alternative is to use > soapsuds parameter -gc to generate the code verse > -oa:<assembly>.dll this also deviates from namespace > clashing. If you are > using configuration files you cannot use interfaces or > abstract classes you > need to use the soapsuds generated metadata.
I figured out that the problem arose from the fact that my interface was both implemented both in a specific assembly AND in the generated dll. The compiler always took the interface in the dll - so the compiler says - and BANG. Do you happen to know how to tell VS.NET what assembly to take during compilation when there are two definitions with identical names in two separate assemlbies? BTW I solved the issue not by generating a dll, but a .cs file by using -gc like you suggested. I got two files - one with the soap 'stub' and one with an interface implementation. I discarded the last one and included the first one in my client project, and presto. Seems like a pretty tiresome way to get this right. > Are you using a Window Service to host your remoted Object? > If so I have a question for you. Not yet, so you might want to save your question for someone else ;-) Rgds, Joost You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
