Convert::ToInt64 Method (String^, Int32)
Converts the string representation of a number in a specified base to an equivalent 64-bit signed integer.
Assembly: mscorlib (in mscorlib.dll)
Parameters
- value
-
Type:
System::String^
A string that contains the number to convert.
- fromBase
-
Type:
System::Int32
The base of the number in value, which must be 2, 8, 10, or 16.
Return Value
Type: System::Int64A 64-bit signed integer that is equivalent to the number in value, or 0 (zero) if value is null.
| Exception | Condition |
|---|---|
| ArgumentException | fromBase is not 2, 8, 10, or 16. -or- value, which represents a non-base 10 signed number, is prefixed with a negative sign. |
| ArgumentOutOfRangeException | value is String::Empty. |
| FormatException | value contains a character that is not a valid digit in the base specified by fromBase. The exception message indicates that there are no digits to convert if the first character in value is invalid; otherwise, the message indicates that value contains invalid trailing characters. |
| OverflowException | value, which represents a non-base 10 signed number, is prefixed with a negative sign. -or- value represents a number that is less than Int64::MinValue or greater than Int64::MaxValue. |
If fromBase is 16, you can prefix the number specified by the value parameter with "0x" or "0X".
Because the negative sign is not supported for non-base 10 numeric representations, the ToInt64(String^, Int32) method assumes that negative numbers use two’s complement representation. In other words, the method always interprets the highest-order binary bit of a long integer (bit 63) as its sign bit. As a result, it is possible to write code in which a non-base 10 number that is out of the range of the Int64 data type is converted to an Int64 value without the method throwing an exception. The following example converts MaxValue to its hexadecimal string representation, and then calls the ToInt64(String^, Int32) method. Instead of throwing an exception, the method displays the message, "0xFFFFFFFFFFFFFFFF converts to -1."
When performing binary operations or numeric conversions, it is always the responsibility of the developer to verify that a method is using the appropriate numeric representation to interpret a particular value. As the following example illustrates, you can ensure that the method handles overflows appropriately by first determining whether a value represents an unsigned or a signed type when converting it to its hexadecimal string representation. Throw an exception if the original value was an unsigned type but the conversion back to an integer yields a value whose sign bit is on.
The following example attempts to interpret each element in a string array as a hexadecimal string and convert it to a long integer.
Available since 8
.NET Framework
Available since 1.1
Portable Class Library
Supported in: portable .NET platforms
Silverlight
Available since 2.0
Windows Phone Silverlight
Available since 7.0
Windows Phone
Available since 8.1