Chris,

The answer of how many dlls to create depends on the context of your applications. If there are business objects specific to an application that will never be reused in other applications then those can be isolated from the others. Also, for ease of maintenance, I would try to organize the business objects in groups that make sense to the context of your applications. If you need to deploy a compact framework app where resources are more limited, then breaking apart the assemblies is more important. You would only want to include the business objects that would be used in the app. and try to minimize the extra classes not needed.


>Thanks Cathi - can I just verify, I would create a Window Application project for front end and Class Library projects for the other two tiers?
>One question leads to another!! If I have created a class library project for data and business layers presumably this will build into two big dll's - is this OK or should I be aiming at a number of smaller dll's per layer?
>Thanks for your advice!