Communication Framework between Windows Services and Application

Writing two Windows Services and one Application (no user interface required), which reside on the same or different computers in the same domain and are able to communicate. You will not have to code any functions, just the skeleton/framework which allows communication. You will have to implement empty functions which can be called remotely and answer the call by returning a string. All parameters for testing purposes will be strings. One of the services needs to be able to run in more than one instance at the same time. When the service starts, it read a registry key, which returns a number Instances between one and Max, where Max is a coded constant and currently Max=10 (if the registry key doesn't exist default is 1). Then it opens instance threads according to the number of requested Instances. The service will only need to be installed once, but the part of the program that communicates needs to run parallel. See attached diagram for more details about the framework needed. Please describe, how you would solve the following problems: 1. How you want to handle communication: RPC, WebServices, etc. 2. Find services on the network, broadcasting. 3. How you want to handle permissions, e. g. the application may run under credentials of a user, whereas the Windows Services run as system account. 4. Though building a setup project is not part of this job, a small documentation on how to install and uninstall your services manually is needed. Please let me know, if you did something similar in the past. I think, what I need is pretty easy, if you know how it must be done. Let me know if you see any points that I left open (I do not have much experience in the area of Windows Services). ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform Programming platform and language: VB.net The services will need to run on Windows 2000 Server and Windows Server 2003, whereas the application will be running on Windows 2000, XP Home or XP Professional.