Moving from VB6 - API Long now Integer?

[Jerry West]

I am moving from VB6 to VB .NET so please bear with me. Should I change all
of my API declarations in VB6 that declared Longs to Integers? For example
in VB6:

Declare Function GetClientRect Lib "user32" (ByVal hWnd as Long, ByVal
lpRect as RECT) As Long

Should this now read:

Declare Function GetClientRect Lib "user32" (ByVal hWnd as Integer, ByVal
lpRect as RECT) As Integer

Thanks,

JW

[Herfried K. Wagner [MVP]]

"Jerry West" <[e-mail]:

So should anything declared as Integer in VB6 be declared as a Short on
.NET?

Not necessarily anything. It really depends on the types used in the C
function prototype.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>

[Armin Zingler]

"Jerry West" <[e-mail]

So should anything declared as Integer in VB6 be declared as a Short
on .NET?

For API declarations this is correct. 16 bit integers are called Short now.

But in general, if you need to declare an integer variable and if it's size
is not predetermined externally, you should use the Integer (=Int32) data
type because it's considered being the native Integer data type size, just
like it was common practice to use Long in VB6 for the same reason.
(Though, I don't know if this is still a common rule with 64-bit processors
and 64-it OSes now. Anybody knows?)
Armin