solution reference and namespace issue

Question

1.00/5 (1 vote)

See more:

in a c# solution when we add different projects.I have two questions :
1) why we give reference to the other project? can't we just use inheritance???
2) After we give the reference by using the visual studio IDE why we have to add the project to the namespace system??? for example: using blog.entity; i thought that much intelligent IDE would do that.

thanks in advance for your replies that informs and enlighten.

C#

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using Blog.Entity;
using System.Data.SqlClient;
using System.Data;

Posted 9-Jul-12 0:59am

y.baris

Updated 9-Jul-12 1:00am

Manas Bhardwaj

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Accepted Answer · 2012-07-09T01:11:00

Becaue you aren't ingheriting anything by default.
Adding a reference tells VS that you want to refer to classes within the DLL - either by instantiation them:

C#

MyDLLClass instance = new MyDLLClass();

Or by using the static methods:

C#

string myString = MyDLLClass.StaticMethod();

In addition, you can use these classes as a basis for your ouwn classes via inheritance:

C#

public partial class MyClass : MyDLLClass
   {
   ...

But just because you can reference a class within a DLL file, doesn't mean that you want to in every file: the using namespace statemkent just lets VS accept a shortcut: instead of having to type

C#

string s = MyDLLNamepace.MyDLLCLass.StaticMethod();

each time, you can just type the shorter version:

C#

string s = MyDLLCLass.StaticMethod();

But you might not want that in every file - what if you have MyDLLClass in two DLL files, under different namespaces? If it added a using to every file automatically when you added a reference, then any existing uses would have a problem trying to work out which version you meant to write.