On Nov 18, 12:01*pm, Family Tree Mike
<FamilyTreeM...@discussions.microsoft.comwrote:
Quote:
"Curious" wrote: Quote:
I was asked to create a C#.NET Console Library project that contains
two sub-libraries. And each sub-library contains multiple utilties.
| > Quote:
As an experiment, I've created a Console Library project (solution).
Then I've added two projects (they're supposed to be sub-libraries).
However, each project has its own indepent assembly in the form of
a .dll file.
| > Quote:
It seems that there is no way I can create a unified assembly (a
single .dll file) containing both projects (or libraries). Any input
on how to solve this problem? I work with business people who don't
know .NET and they request me to do it this way.
| >
You could ask them what they mean...
>
My first impression though would be to create two folders such as SubLib1
and SubLib2 in your single library project. *This gives the classes created
in each folder different namespaces such as Project.SubLib1.Class1,
Project.SubLib2.Class2. *It still compiles to a single dll. *You don't need
to put the classes in separate folders as you could simply change the
namespaces in the class files, but I find it easier to manage them this way.
|
They want a single assembly that contains a hierarchy of namespaces.
For instance, the assembly is "Utilities". There are two sub-libraries
(sub-namespaces) under "Utilities" called "Lib1" and "Lib2".
When I use each library, I use either namespace "Utilities.Lib1" or
namespace "Utilities.Lib2".
Question regarding your suggestion: I believe by project, you mean
"solution". Is that the case? Do I need to create multiple projects
under the solution for multiple sub-libraries? I guess not, because
that would result in multiple assemblies.
Shall I manually add the folders on the hard drive when I create the
project? How will the solution/pro