by Bernard T
This week’s blog’s assignment gave us a choice between several topics; I chose to do mine on Namespaces, more specifically .NET Namespaces. Namespaces, the article mentioned enables users to group logically related classes together but points out that classes are not required to be provided to use a Namespace. Namespaces are a collection of objects, each containing different sets of objects grouped according to their functionality. Advantages of Namespaces include preventing naming collisions; this means that if for example two or more companies produce a component with the same name, Namespaces will provide a way to distinguish them from each other. Namespaces also has the added benefit of making it easier to understand the purpose of a given class, grouping your classes that manipulate images together for example into a System.Drawing namespace makes it easier to remember what and where the classes are. The article gave numerous examples of Namespaces; System.Data is one that contains all the classes needed to interact with data sources and without it, it would be impossible for .NET to function compatibly with Active X Data Objects for .NET. The article also pointed out however, that some Namespaces are automatically imported into ASP.NET.
The articles I read did a good job of explaining what Namespaces do and what they were used for. Many examples were given to what typical Namespaces do and what goes into making a proper one. It also gave examples on how to implement Namespaces by showing the reader how to code them properly into different formats. The examples given also showed how to use Namespace statements to group components and how those components in different files could share the same Namespace and also how those different components in the same file can occupy different Namespaces. The articles are not going to make someone an expert but it did give enough insight so that the reader can get a basic understanding of what Namespaces are used for.
I believe that the articles relate to our class because of how it explained what Namespaces do and how they should be implemented into our subject. I was hoping that sharing what I learned from the articles would give whoever reads this blog a little bit more closer to understanding what Namespaces are and what they are used for.
Abhimanyu, K. (2012, May 12). Using component (declaring namespace) in asp.net – part 6. ITORIAN: Abhimanyu’s Thoughts, 1(6), 12. Retrieved from http://www.itorian.com/2012/0