1
Reply

Best Approach - Opinions Please - Windows Service -vs- WCF Service -vs- other

Joe Marley

Joe Marley

Apr 9 2009 5:21 PM
10.7k

My development environment is Visual Studio 2008 C#.

I have 2 apps.  An app created by another team has requirements that they call an .EXE (my app) MANY, MANY, MANY times.  My app accepts command line args of variable length character and numeric data.

My app works fine however there is concern that a delay of (3 - 9 seconds) due to various things (network connectivity, etc. etc.) may be deemed unacceptable.

The delay comes from overhead in the app on initialization.

If I could put it into a service - my thought is I pay once for the overhead and then the users can have faster response time.

Few questions:

1)   Opinions on WCF Servive -vs- Windows Service.

What I've found so far is that examples of Windows Service in C# only seem to be able to accept numeric constants that to the service program would mean something.  I know very little about WCF Services and it appears that they are more used for Web development. 

Can they even be used in conjunction with windows applications designed for the desktop?

Is there too much of a headache doing one vs other?Note: Security is not an issue with the parameters as there is nothing sensative about this particular data.

2) Any books / links - i.e. suggested reading to get up to speed on either approach

 

Any suggestions are greatly GREATLY appreciated

Thanks Much

JFMarley


Answers (1)