Search code examples
c#wpfdllconventions

Library Structure Convention

According to Names of Assemblies and DLLs, your library should be named by the following convention: <Company>.<Component>.dll. The problem is when you library incorporate projects like WPF Effects (special project that provide the effect build action) or WPF Custom Controls. Should you break the convention and have DLLs as follows:

MyCompany.MyLibrary.dll
MyCompany.MyLibrary.MyEffects.dll
MyCompany.MyLibrary.MyCustomControls.dll

Is there a way of combining all the different projects into a single DLL?

Solution

  • As mentioned in comments, you might be happy with putting all the code into one project and just namespace it accordingly.

    In case it is your requirement to have separate assemblies you can merge it using Microsoft's ILMerge or with opensource ILRepack.