Convert::ToByte Method (String^, Int32)
Converts the string representation of a number in a specified base to an equivalent 8-bit unsigned 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::ByteAn 8-bit unsigned 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 unsigned 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 base 10 unsigned number, is prefixed with a negative sign. -or- value represents a number that is less than Byte::MinValue or greater than Byte::MaxValue. |
If fromBase is 16, you can prefix the number specified by the value parameter with "0x" or "0X".
Because the Byte data type supports unsigned values only, the ToByte(String^, Int32) method assumes that value is expressed using unsigned binary representation. In other words, all eight bits are used to represent the numeric value, and a sign bit is absent. As a result, it is possible to write code in which a signed byte value that is out of the range of the Byte data type is converted to a Byte value without the method throwing an exception. The following example converts MinValue to its hexadecimal string representation, and then calls the ToByte(String^, Int32) method. Instead of throwing an exception, the method displays the message, "0x80 converts to 128."
When performing binary operations or numeric conversions, it is always the responsibility of the developer to verify that a method or operator is using the appropriate numeric representation to interpret a particular value. The following example illustrates one technique for ensuring that the method does not inappropriately use unsigned binary representation when it converts a hexadecimal string representation to a Byte value. The example determines whether a value represents a signed or an unsigned integer while it is converting that value to its string representation. When the example converts the value back to a Byte value, it checks whether the original value was a signed integer. If so, and if its high-order bit is set (which indicates that the value is negative and that it uses two's complement instead of unsigned binary representation), the method throws an exception.
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