Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m currently developing a .NET Windows Service and am curious about how references vs. namespaces work on a high level. I come from a C++ background and am only familiar with statements like #include <…> etc. Thanks for the clarification.
A reference is simply a way to tell the compiler to look in the referenced assembly for types when trying to resolve them.
Now, namespaces are not tied to assemblies. Namespaces are a logical construct while assemblies are a physical construct.
This is why you see classes in .NET from the System namespace in mscorlib.dll, System.dll, System.Core.dll, etc, etc.
So while you can have tremendous overlap between the two, you should avoid leaking your namespace across too many assemblies.
I take a assembly-per-namespace approach (the assembly only has types from one namespace, assuming it is specialized), but your approach may vary.
Generally though, keep the namespace bleed small (or none at all) and you will generally be fine.