Hi, just a question concerning the software architecture. I don't know how to split up smartly the file types in different assemblies .

I have four types of files.
- mapping files (*hbm.xml)
- entity classes, which represent my tables
- Data Access Classes, which work with my entity classes - its a abstraction layer between entity and business classes, so I do not smutch neither one of them
- Business Classes, which use the Data from the Access Classes within the Business Logic defintion

mapping and entity files are generated. If something changes in the data model I do not have to transfer addition coding from my former entity classes, but I just replace the old ones with the new ones. Manual code changes will be only made in the access class.
The application will be shipped to many customers and needs to be maintained efficiently.

Which file types would you combine in one assembly?

Thanks in advance

antoschka

There is no final answer to this, some people prefer few assemblies and others many. Often et follows the way you structure your projects in Visual Studio.

But watch out for circular dependencies if you decide on many assemblies.

For a discussion on the topic watch the comments here:
http://ayende.com/Blog/archive/2008/02/ ... ution.aspx
and here:
http://ayende.com/Blog/archive/2008/02/ ... embly.aspx