Using .NET 3.5:
I plan to build a .NET windows service application that will serve as a task scheduler that launches .NET assemblies. (yes there is a reason I am not using windows task scheduler for this).
I also want to create a .NET GUI that will allow a user to manage the service. I need to have more control/flexibility than the System.ServiceProcess.ServiceController provides.
For Example if my service has a method MakeANoise(param1, param2) I want to be able to invoke this from my GUI application.
Both applications will be running on the same machine.
My first thoughts were to use System.Net.Sockets and communicate to the service over TCP/IP, but I'm wandering if there are other better solutions for what I want to do. Would WCF be a good solution for this?