Assuming your server is .NET 2.0 application then WSE 3.0 is a possible
method you could use; as per the previous post. To elaborate you could WSE
enable your service and use the TCP transport mechanism to communicate to
your service using SOAP over the TCP protocol assuming you wanted to keep
this all in process?
Essentially within your service you can derive a class from SoapService and
register it with the SOAPReceivers collection specifying the endpoint
reference of your server host ip and a desired port to listen on.
Within your client application you can derive from SoapClient and
communicate via an endpoint reference to the ip/port that your service is
listening on.
There are samples that show this within the WSE 3.0 SDK download.
Rgds,
Tim.
"Diego L Espiñeira" wrote:
Hi, all
I've got a windows service (server) application and a winforms (client)
application. What I need to do is to host a web service in the windows
service application so the client can request information about its current
state and request server's internal data to change on user's behalf, plus I
need to do it in a standard compliant way, such as xml/web services.
Any help/link/info would be very apreciated
Thanks