... if there is such a thing. Here's an image of two approaches for structuring DLLs / links in a .NET application: http://www.experts-exchange.com/images/t80668/compArch.png . The application may be a website (in this case) or winform. Each box is a DLL. For a winform application, simply replace "webcontrols" with "winformcomponents".
The first (top) image is what I like. You might want to extend “some” of the basic web controls and use others directly. The second image allows you to extend any web controls through the interface. This seems redundant to me, as you can just use what already exists unchanged. Which is better and what are the advantages / disadvantages?
The first image places the lowest common constructs (exceptions, fileIO, constants, etc.) in the common.dll file. The second image puts the business logic of the application and is distributed in one DLL. Which is better and what are the advantages / disadvantages of each apporach?
source
share