B
Bob Weiner
Hi,
I am an IT person who uses .Net to support our infrastructure. Since I have
been doing this for a while it would be a misnomer for classify myself as a
newbie; perpetual amatuer seems more appropriate.
Notwithstanding, I am tired of cutting and pasting code and moving classes
from one project to the next and would like to know the "proper" way to
store code for reuse. I have used .dll's with some success but am still not
organized.
Ideally, I'd like to have a hierarchial namespace with "myOrg" at the root.
Underneath I should find myOrg.AD, myOrg.AD.Queries, myOrg.Exchange... I
assume professional developers do it this way.
I have seen a lot on Namespaces but I haven't been able to conceptually move
from the simple concept of scope to that of organizing code for reuse.
Does this happen by creating a 1 dll / namespace, copying that dll into a
matching directory structure, then adding a reference to each dll in all
subsequent projects?
advice or referrals would be greatly appreciated.
Thanks, bob
I am an IT person who uses .Net to support our infrastructure. Since I have
been doing this for a while it would be a misnomer for classify myself as a
newbie; perpetual amatuer seems more appropriate.
Notwithstanding, I am tired of cutting and pasting code and moving classes
from one project to the next and would like to know the "proper" way to
store code for reuse. I have used .dll's with some success but am still not
organized.
Ideally, I'd like to have a hierarchial namespace with "myOrg" at the root.
Underneath I should find myOrg.AD, myOrg.AD.Queries, myOrg.Exchange... I
assume professional developers do it this way.
I have seen a lot on Namespaces but I haven't been able to conceptually move
from the simple concept of scope to that of organizing code for reuse.
Does this happen by creating a 1 dll / namespace, copying that dll into a
matching directory structure, then adding a reference to each dll in all
subsequent projects?
advice or referrals would be greatly appreciated.
Thanks, bob