Hi,
We have a set of classes that we use to transfer data in our web
services (data transfer objects). These classes are in a special
project. Both our web services themselves, and our clients have
reference to the assembly containing these classes.
In order to use these data transfer object classes, with VS .NET 2003,
we would generate a web reference, and then delete the generated proxy
classes, and add references to our own classes. Mind you we would leave
the methods themselves, we would just delete the type classes so that
we could use the ones in our assembly. This was somewhat tedious, but
it worked.
In VS .NET 2005, it looks like this is much more difficult because VS
..NET generated proxy files have the methods and the data classes mixed
together. So it's not just one block of code.
Is anyone else running into this problem? Any suggestions, maybe a
better way to handle this?
I think I can set the namespace on the proxy, but I don't really want
to use the proxy at all for these classes. And the generated proxy
classes are not the same as the ones we write - they miss any
non-public methods for example.
Thanks!
Secret Squirrel