UnicodeEncoding.GetBytes Method (Char*, Int32, Byte*, Int32)
Encodes a set of characters starting at the specified character pointer into a sequence of bytes that are stored starting at the specified byte pointer.
This API is not CLS-compliant. Namespace: System.Text
Assembly: mscorlib (in mscorlib.dll)
[ComVisibleAttribute(false)] [CLSCompliantAttribute(false)] public override int GetBytes( char* chars, int charCount, byte* bytes, int byteCount )
- Type: System.Char*
A pointer to the first character to encode.
- Type: System.Int32
The number of characters to encode.
- Type: System.Byte*
A pointer to the location at which to start writing the resulting sequence of bytes.
- Type: System.Int32
The maximum number of bytes to write.
Return ValueType: System.Int32
The actual number of bytes written at the location indicated by the bytes parameter.
chars is null (Nothing).
bytes is null (Nothing).
charCount or byteCount is less than zero.
Error detection is enabled, and chars contains an invalid sequence of characters.
byteCount is less than the resulting number of bytes.
A fallback occurred (see Character Encoding in the .NET Framework for fuller explanation)
To calculate the exact array size that GetBytes requires to store the resulting bytes, the application uses GetByteCount. To calculate the maximum array size, the application should use GetMaxByteCount. The GetByteCount method generally allows allocation of less memory, while the GetMaxByteCount method generally executes faster.
With error detection, an invalid sequence causes this method to throw a ArgumentException. Without error detection, invalid sequences are ignored, and no exception is thrown.
Data to be converted, such as data read from a stream, might be available only in sequential blocks. In this case, or if the amount of data is so large that it needs to be divided into smaller blocks, the application should use the Decoder or the Encoder object provided by the GetDecoder or the GetEncoder method, respectively.
To ensure that the encoded bytes are decoded properly, the application should prefix encoded bytes with a preamble.
Requires full trust for the immediate caller. This member cannot be used by partially trusted or transparent code.