Option Strict Error on Const declaration.....

[Smith Guy]

After declaring

Option Strict On

Iam getting the error on.

Private Const ERROR_SUCCESS = &H0

What is the correction needed for the above statement.

..Net Framework 1.1.

Thanks,

Smith

 

[Oenone]

Private Const ERROR_SUCCESS = &H0

Private Const ERROR_SUCCESS As Integer = &H0

 

[Ken Tucker [MVP]]

Hi,

Private Const ERROR_SUCCESS as integer = &H0

Ken
----------------
After declaring

Option Strict On

Iam getting the error on.

Private Const ERROR_SUCCESS = &H0

What is the correction needed for the above statement.

..Net Framework 1.1.

Thanks,

Smith

 

[Herfried K. Wagner [MVP]]

Option Strict On

Iam getting the error on.

Private Const ERROR_SUCCESS = &H0

What is the correction needed for the above statement.

\\\
Private Const ERROR_SUCCESS As Int32 = &H0
///

 

[Phill. W]

\\\
Private Const ERROR_SUCCESS As Int32 = &H0
///

Herfried,

Probably been asked before (apologies), but why do you favour
"Int32" over "Integer"? Is it just for clarity or are Our Friends in
Redmond planning to "upgrade" Integer to its 64-bit equivalent
any time soon?

TIA,
Phill W.

 

[Herfried K. Wagner [MVP]]

Probably been asked before (apologies), but why do you favour
"Int32" over "Integer"?

I prefer to use the names of the types in the .NET Framework when dealing
with unmanaged code. It's only my personal preference.

Is it just for clarity or are Our Friends in
Redmond planning to "upgrade" Integer to its 64-bit equivalent
any time soon?

'Integer' will remain 32-bit even in the 64-bit world.