This print for content only-size & color not accurate 7" X 9-1/4" / casebound / malloy

// Hello world in C#

using System;

public class MyApp

{

static void Main()

{

Console.WriteLine("Hi from C#");

}

}

' Hello world in VB

Imports System

Public Module MyApp

Sub Main()

C H A P T E R   1  

■

T H E   P H I L O S O P H Y   O F   . N E T

24

8849CH01.qxd  10/1/07  10:30 AM  Page 24

---

Console.WriteLine("Hi from VB")

End Sub

End Module

// Hello world in C++/CLI

#include "stdafx.h"

using namespace System;

int main(array ^args)

{

Console::WriteLine(L"Hi from C++/CLI");

return 0;

}

Notice that each language is making use of the Console class defined in the System namespace.

Beyond minor syntactic variations, these three applications look and feel very much alike, both

physically and logically. 

Clearly, your primary goal as a .NET developer is to get to know the wealth of types defined in

the (numerous) .NET namespaces. The most fundamental namespace to get your hands around is

named System. This namespace provides a core body of types that you will need to leverage time

and again as a .NET developer. In fact, you cannot build any sort of functional C# application with-

out at least making a reference to the System namespace, as the core data types (System.Int32,

System.String, etc.) are defined here. Table 1-3 offers a rundown of some (but certainly not all) of

the .NET namespaces grouped by related functionality.

Table 1-3.

A Sampling of .NET Namespaces