Alternatively, you might consider using WCF rather than ASP.NET Web
Services.
WCF will allow your app to create a proxy through which you can consume
remote web services (I.e. out of process or hosted on a different machine)
and also expose itself as a web service for others to consume.
Note that WCF will also allow you to use a variety of transports (e.g. HTTP,
TCP) and encodings (e.g. SOAP, POX, BinaryXML) depending on your needs, just
by changing the app config file!
--- BitCrazed ---
"davidkclark" <da*********@gmail.comwrote in message
news:f9**********************************@56g2000h sm.googlegroups.com...
This article on msdn decribes how to host a webservice in a
windowsservice:
http://msdn2.microsoft.com/en-us/library/aa529311.aspx
Hosting in your client program should be similar. Basically you will
have to copy the source and config files for your webservice, add
usings for the appropriate Microsoft.Web.Services classes, and call
SoapReceivers.Add to start and .Clear to stop the service.
BTW: You might be better off looking into .Net Remoting if you are
looking for communication between applications (TCP or IPC depending
on the location fo the two clients)
Good Luck.