To separate or not to separate biz & data layers in to each project in .NET
<p>Currently I have separate project for my business logic and a separate project for my data access. I then have various other projects for a shopping cart site, an intranet, an extranet, etc. These sites all use the biz &amp; data projects mentioned above. </p>

<p>My task today was to have all these projects use a single DLL of the biz &amp; data projects on the server. I know right now the projects are just copying the DLL locally to the project. Then I got to thinking-- I am going to be making significant changes to the Cart Site, including DB schema changes, so I will have to update the DL &amp; BL. So if I copy up a new DLL how am I supposed to remember if it is going to break something else? I am looking at this all the wrong way? Should I have a biz logic and data access for each project separate rather than centralized?</p>
