Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.
Course Of The Month
8 days, 15 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Namespace concept
Posted on 2007-11-14
In asp.net, what is the concept of the Namespace?
I mean, I am looking at a Custom MembershipUser, at the top it has a Namespace of say, MyNameSpace....
within this MembershipUser, it implements a custom ObjectBase class, which also has the namespace MyNameSpace.
Then in this example I'm looking at, there are a couple of other custom classes and they have a namespace of, for example:
MyNameSpace.Stuff
Why do you create this "Stuff" sub namespace? What is that called anyway? and why?
I have read this:
http://msdn2.microsoft.com/en-us/library/0dx91cw5(VS.80).aspx
So please don't send me to a URL.
For instance.. it says:
>>causes the source code following the declaration to be compiled within that namespace
So what are the benefits of compiling into a namespace?
Just a one paragraph explanation explaining why you use it, the benefits, etc. Not looking for a book, just something you'd explain to a trainee at the coffee pot about namespaces in human language.
Now, in the above url, it says this:
>>Adding to a Namespace. If a namespace is already defined, even outside your project, you can add programming elements to it. To do this, you use a Namespace statement to direct Visual Basic to compile the following elements into that namespace.
It shows an example of using this namespace:
Namespace System.Collections.Generic
But that is an existing namespace. Why would you add to an existing System namespace?
I mean, I am looking at a Custom MembershipUser, at the top it has a Namespace of say, MyNameSpace....
within this MembershipUser, it implements a custom ObjectBase class, which also has the namespace MyNameSpace.
Then in this example I'm looking at, there are a couple of other custom classes and they have a namespace of, for example:
MyNameSpace.Stuff
Why do you create this "Stuff" sub namespace? What is that called anyway? and why?
I have read this:
http://msdn2.microsoft.com/en-us/library/0dx91cw5(VS.80).aspx
So please don't send me to a URL.
For instance.. it says:
>>causes the source code following the declaration to be compiled within that namespace
So what are the benefits of compiling into a namespace?
Just a one paragraph explanation explaining why you use it, the benefits, etc. Not looking for a book, just something you'd explain to a trainee at the coffee pot about namespaces in human language.
Now, in the above url, it says this:
>>Adding to a Namespace. If a namespace is already defined, even outside your project, you can add programming elements to it. To do this, you use a Namespace statement to direct Visual Basic to compile the following elements into that namespace.
It shows an example of using this namespace:
Namespace System.Collections.Generic
But that is an existing namespace. Why would you add to an existing System namespace?
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
2 Comments
>>In asp.net, what is the concept of the Namespace?
>>Why do you create this "Stuff" sub namespace? What is that called anyway? and why?
>>So what are the benefits of compiling into a namespace?
In my opinion, in practice, namespaces are just housekeeping.
How do you want to group and organize your code?
Usage of namespaces (again, just in my experience) is going to be defined either by company standards or the developer.
>>Why would you add to an existing System namespace?
Again, just housekeeping.
If you write some code that manipulates text, do you want it in your own namespace and class and use it with something like "MyNamespace.MyTextFunctio
or do you feel it's good enough to be part of System.Text?
and then call it with "System.Text.MyTextFunctio
>>Why do you create this "Stuff" sub namespace? What is that called anyway? and why?
>>So what are the benefits of compiling into a namespace?
In my opinion, in practice, namespaces are just housekeeping.
How do you want to group and organize your code?
Usage of namespaces (again, just in my experience) is going to be defined either by company standards or the developer.
>>Why would you add to an existing System namespace?
Again, just housekeeping.
If you write some code that manipulates text, do you want it in your own namespace and class and use it with something like "MyNamespace.MyTextFunctio
or do you feel it's good enough to be part of System.Text?
and then call it with "System.Text.MyTextFunctio
Hi,
A namespace is basically a way to group together classes that perform a common goal, or that have some kind of relationship between them, usually what I do is create one general namespace say MyApp and start distributing the classes that I use in my project in different sub-namespaces, something like MyApp.Data, MyApp.ErrorHandling, MyApp.Controls, etc. that way you get a nice separation of the different layers in the structure of your application.
I don't believe it's a good practice to add to any of the existing namespaces in the .NET framework, that would just create confusion to anybody using your classes and result in not being able to tell which assemblies are needed as references to a project in order to use them.
A namespace is basically a way to group together classes that perform a common goal, or that have some kind of relationship between them, usually what I do is create one general namespace say MyApp and start distributing the classes that I use in my project in different sub-namespaces, something like MyApp.Data, MyApp.ErrorHandling, MyApp.Controls, etc. that way you get a nice separation of the different layers in the structure of your application.
I don't believe it's a good practice to add to any of the existing namespaces in the .NET framework, that would just create confusion to anybody using your classes and result in not being able to tell which assemblies are needed as references to a project in order to use them.
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Just a quick little trick I learned recently. Now that I'm using jQuery with abandon in my asp.net applications, I have grown tired of the following syntax:
(CODE)
I suppose it just offends my sense of decency to put inline VBScript on a…
This article shows how to deploy dynamic backgrounds to computers depending on the aspect ratio of display
In this video, viewers are given an introduction to using the Windows 10 Snipping Tool, how to quickly locate it when it's needed and also how make it always available with a single click of a mouse button, by pinning it to the Desktop Task Bar.
Int…
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
Suggested Courses
Earn Certification
HTML5 Specialist - Certification
Free withPremium
Course of the Month8 days, 15 hours left to enroll
617 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.