C# architecture for long-lived data collecting server apps

Question

We are about to start a new project for a server application, for the purpose of collecting data from several data sources and storing it in a database.

For a quick test, we created a WinForms app which uses the core functionality from a custom library, and now have to start migrating it towards the final product.

From what we've done so far, the best way to do this should be to make it a Windows service and then expose basic monitoring and configuration to a thin Win or Web client through remoting/web services.

Is there a more appropriate way to make such an application?

Answer 1

You could consider exposing the service itself using the WCF/ADO.NET Data Services: http://msdn.microsoft.com/en-us/library/cc668792.aspx

Also see this for a quick walkthrough on how to expose a WCF Data Service: http://www.msteched.com/2010/NorthAmerica/DEV324