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

CTS Data Type

VB .NET Keyword

C# Keyword

C++/CLI Keyword

System.Byte

Byte

byte

unsigned char

System.SByte

SByte

sbyte

signed char

System.Int16

Short

short

short

System.Int32

Integer

int

int or long

System.Int64

Long

long

__int64

System.UInt16

UShort

ushort

unsigned short

System.UInt32

UInteger

uint

unsigned int or unsigned long

System.UInt64

ULong

ulong

unsigned __int64

System.Single

Single

float

Float

System.Double

Double

double

Double

System.Object

Object

object

Object^

System.Char

Char

char

wchar_t

System.String

String

string

String^

System.Decimal

Decimal

decimal

Decimal

System.Boolean

Boolean

bool

Bool

Given the fact that the unique keywords of a managed language are simply shorthand nota-

tions for a real type in the System namespace, we no longer have to worry about overflow/underflow

conditions for numerical data, or how strings and Booleans are internally represented across differ-

ent languages. Consider the following code snippets, which define 32-bit numerical variables in C#

and VB .NET, using language keywords as well as the formal CTS type:

// Define some "ints" in C#.

int i = 0;

System.Int32 j = 0;

' Define some "ints" in VB .NET.

Dim i As Integer = 0

Dim j As System.Int32 = 0

Understanding the Common Language

Specification

As you are aware, different languages express the same programming constructs in unique, lan-

guage-specific terms. For example, in C# you denote string concatenation using the plus operator

(+), while in VB .NET you typically make use of the ampersand (&). Even when two distinct lan-

guages express the same programmatic idiom (e.g., a function with no return value), the chances

are very good that the syntax will appear quite different on the surface: