I am starting a new Silverlight 3 project in Visual Studio 2010. My plan is to have a project for each of these:
The Silverlight application
The hosting web application
The WCF service
This last one will also contain a typed dataset (that will serve as my data logic layer) and a few classes to do my business logic. The WCF service methods will return typed data to Silverlight.
I am just wondering if there is any compelling reason to split the BLL components out of the WCF service project. Any other comments about organizing the project are welcome, too, of course. One thing I will not entertain is using some ORM like N-Hibernate. The entire solution needs to be constructed with the more-than-capable tools that come with Visual Studio. Thank you!
Best Answer
The project I work on at work has separate projects for the business components. I really think it depends on the size of the project. It might make sense in a large project to do this, especially if multiple parts of your project would be sharing the same BLL.