With reference to this question, I would like to know which version (.net 4.0 client profile or full version) should be used for Windows service application and why?
3
votes
I can't remember the exact issue I had with using the client, but you want full version. I'll try to find why.
– Stefan H
@Stefan H: If you can recollect the issue you had with client profile, it would be great help for me. I'll be developing a windows service application which will do multi threading for importing data from various external sources. I dont want to pull down my server because of framework issues.
– JPReddy
The .NET Framework 4 Client Profile does not include the following features. You must install the .NET Framework 4 to use these features in your application: ASP.NET Advanced Windows Communication Foundation (WCF) functionality .NET Framework Data Provider for Oracle MSBuild for compiling
– Stefan H
@Stefan H: Even I read those points just now msdn.microsoft.com/en-us/library/cc656912.aspx. I think I dont require any of those extra features of full version.
– JPReddy
1 Answers
6
votes
The project templates for Windows Services target the client profile by default so the choice simply comes down to 2 aspects:
a) What framework features does your service need - is everything you need available in the client profile or are you going to be using features that are only in the full framework?
b) Does the size of you installation package matter? E.g. If you're package is downloaded and bandwidth is a cost for you then keeping your install package small is clearly a benefit. If this is an internally used service then the size of the install package is likely to be less of an issue.
