How to structure my web service factory projects

Topics: General Discussion Forum, July and December Releases Forum
Dec 13, 2007 at 4:54 PM

Our web services development team is currently using Web Service Factory to create ASMX web services. When we started to develop, each one of the programmer created its own project for every Web Service. So there are 25 web services, with 25 Project of Services Layer, 25 Projects of BLL and 25 Projects of DAL.

We are considering create only three solutions. The first solution would be for the DAL, which most likely will be Auto Generated with LLBL GEN PRO instead of using the Data Access Guidance Package. The second one will be the BLL, which will have a reference to the assembly generated by the DAL; it will include Business Logic and Business Entities projects. Finally, the Service Layer which in our case would have 25 .asmx.

Would this make sense? What would you recommend? Isn’t better to have 25 assemblies working separately than just one big one?

Francisco Pereira
Dec 13, 2007 at 7:27 PM
Regarding the trade off between multiple small dlls vs single big dll, it seems that the general concensus is the latter, as this post mention
Besides the perf reasons, then you may have deplyment (distributed farms, manteinability cases, etc.) and development scenarios (distrubited dev teams) that may require the use of multiple assemblies.