A Service layer can be built on top of the business layer and can expose a set of related Methods. It is pretty common for presentation to consume service which consumes business which consumes data for a 4 layer effect. Also, a service layer should implement processes that ensure that there are at least two different and separate processes - one for the provider and one for the consumer. You can look it all up on MSDN.


>A "service layer" is used to access things outside your application that you need to use. For example, a web service.
>
>As for your current app, you can put WCF in now, then just change the address, and possibly the binding, when you distribute pieces to the server.
>
>
>>
>>What exactly do you mean by a service layer? I think I have heard that term used to mean multiple things.
>>
>>I seem to remember seeing reference to WCF in the documentation. Currently I am doing n-tier architecture with it, but single tier deployment. No advanced communications has entered the picture for me yet. I am using DevForce to extend an older VFP system witch is all single tier. At some point I will be taking the new .NET parts to full n-tier deployment, just not now.