R
Rob R. Ainscough
I'm trying to figure out how Microsoft were able to setup the
namespace/assemblies in such a way that the corresponding Class Library
DLL's seem to be aware of the other Parent/child DLL relationship?
i.e. System (is a System.DLL), System.Data (is System.Data.DLL), etc. etc.
when I try to create my own such structure I can't seem to get it to work.
I create an assembly (new project based on class library) say call
"MyCompany", build solution to a DLL called MyCompany.DLL. The root
namespace for is MyCompany.
I create a 2nd assembly (new project based on class library) say it is
called "Accounting", build the solution to a DLL called Accounting.DLL. I
set the root namespace to MyCompany.
However if I create a 3rd assembly (new project based on WindowsForms) and
add reference "MyCompany" and "Accounting" they do not tier when I use
IMPORTS MyCompany -- I was hoping to see IMPORTS MyCompany.Accounting --
but no such luck.
Should I be using a Single solution with multiple projects? I'm trying to
optimize my DLL usage.
Thanks, Rob.
namespace/assemblies in such a way that the corresponding Class Library
DLL's seem to be aware of the other Parent/child DLL relationship?
i.e. System (is a System.DLL), System.Data (is System.Data.DLL), etc. etc.
when I try to create my own such structure I can't seem to get it to work.
I create an assembly (new project based on class library) say call
"MyCompany", build solution to a DLL called MyCompany.DLL. The root
namespace for is MyCompany.
I create a 2nd assembly (new project based on class library) say it is
called "Accounting", build the solution to a DLL called Accounting.DLL. I
set the root namespace to MyCompany.
However if I create a 3rd assembly (new project based on WindowsForms) and
add reference "MyCompany" and "Accounting" they do not tier when I use
IMPORTS MyCompany -- I was hoping to see IMPORTS MyCompany.Accounting --
but no such luck.
Should I be using a Single solution with multiple projects? I'm trying to
optimize my DLL usage.
Thanks, Rob.