Beginning ASP.NET 4.5 in CSharp and VB Opsylum

Organizing Code x 185
It’s also easy to create your own namespaces. As long as they don’t collide with an existing name,
you can pretty much make up your own namespaces as you see fit. For example, you could wrap the
Calculator class in the following namespace (in Calculator.vb or Calculator.cs in App_Code):
VB.NET
Namespace Wrox.Samples
Public Class Calculator
...
End Class
End Namespace
C#
namespace Wrox.Samples
{
public class Calculator
{
...
}
}
With the calculator wrapped in this namespace, you could create a new instance of it like this:
VB.NET
Dim myCalculator As New Wrox.Samples.Calculator()
C#
Wrox.Samples.Calculator myCalculator = new Wrox.Samples.Calculator();
Although you get some help from IntelliSense to find the Calculator class, typing these long names
becomes boring after a while. Fortunately, there’s a fix for that as well.
After you have created your own namespaces, or if you want to use existing ones, you need to make
them available in your code. You do this with the keyword Imports (in VB.NET) or using (in C#).
For example, to make your Calculator class available in the Calculator demo page without specifying
its full name, you can add the following namespace to your code:
VB.NET
Imports Wrox.Samples
Partial Class Demos_CalculatorDemo
Inherits System.Web.UI.Page
C#
using Wrox.Samples;
public partial class Demos_CalculatorDemo : System.Web.UI.Page
{
With this Imports/using statement in place, you can now simply use Calculator again instead of
Wrox.Samples.Calculator.