I think there are a lot of solution for such an issue. For example, without
IIS, you can create a server appliaction with Sockets and communicate with
TCP. For a solution with IIS (much easy to implment), you may consider a
solution with Web service. For example, a .NET web service running on IIS.
The client can be .NET application or an unmanaged C++ application based on
Following newsgroup should be best place for further questions on Sockets
on Web Service:
If there is any questions, please feel free to let us know.
Microsoft Online Community Support
Get notification to my posts through email? Please refer to
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project ysis and dump ysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
This posting is provided "AS IS" with no warranties, and confers no rights.