This is fine if the types in these shared classes are not passed across
the web service boundary. If they are, then you are going to have problems
with the Xml Serializer, most likely, and modifying the proxy to use the
shared classes.
The easy way to get around it (although tedious), would be to refactor
the classes passed across the web service boundary into interfaces. Then,
in the proxy on the client side, have the proxy class generated by the WSDL
implement the interface, exposing the properties/fields for the class.
Then, you can have your routines work on implementations of the interface.
Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
-
mv*@spam.guard.caspershouse.com
"Jon Skeet [C# MVP]" <sk***@pobox.com> wrote in message
news:MP************************@msnews.microsoft.c om...
<db*****@gmail.com> wrote: This is a very simple question. I have a proxy class (for web service)
and couple of other classes that are common for 3 of my projects. As a
developer, I would like to keep these common classes seperatly and use
them in three different projects. How can I do that?
Create a class library project, put the common classes in that, and
then reference that project (or the DLL it produces if you want it in a
different solution) from the projects which need to use it.
--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too