Out of curiosity, why have you discounted using reflection? If you're okay with using serialization via the [Serializable] attribute -- which is reflection driven -- why have you ruled out doing it yourself? Without knowing exactly what you're doing, it seems like the cost of reflecting against something in-proc would be outweighed by the network transit time of the soap request/response messages...
-Mike http://staff.develop.com/woodring http://www.develop.com/devresources ----- Original Message ----- From: "Sergey Chemishkian" <[EMAIL PROTECTED]> > One way to avoid making extensive use of the Reflections API ... You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
