This topic has not yet been rated - Rate this topic

Marshal.WriteByte Method (IntPtr, Int32, Byte)

.NET Framework 4.5

Writes a single byte value to unmanaged memory at a specified offset.

Namespace: System.Runtime.InteropServices
Assembly: mscorlib (in mscorlib.dll)

static member WriteByte : 
        ptr:IntPtr * 
        ofs:int * 
        val:byte -> unit

Parameters

ptr: Type: System.IntPtr
The base address in unmanaged memory to write to.

ofs: Type: System.Int32
An additional byte offset, which is added to the ptr parameter before writing.

val: Type: System.Byte
The value to write.

Exceptions

Exception	Condition
AccessViolationException	Base address (ptr) plus offset byte (ofs) produces a null or invalid address.

Remarks

WriteByte enables direct interaction with an unmanaged C-style byte array, eliminating the expense of copying an entire unmanaged array (using Marshal.Copy) to a separate managed array before setting its element values.

Examples

The following example demonstrates how to read and write to an unmanaged array using the ReadByte and WriteByte methods.

No code example is currently available or this language may not be supported.

Version Information

.NET Framework

Supported in: 4.5, 4, 3.5, 3.0, 2.0, 1.1, 1.0

.NET Framework Client Profile

Supported in: 4, 3.5 SP1

Portable Class Library

Supported in: Portable Class Library

.NET for Windows Store apps

Supported in: Windows 8

.NET Framework Security

SecurityCriticalAttribute
requires full trust for the immediate caller. This member cannot be used by partially trusted or transparent code.

Platforms

Windows 8, Windows Server 2012, Windows 7, Windows Vista SP2, Windows Server 2008 (Server Core Role not supported), Windows Server 2008 R2 (Server Core Role supported with SP1 or later; Itanium not supported)

The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.

Reference

Marshal Class

WriteByte Overload

System.Runtime.InteropServices Namespace

Copy

Did you find this helpful? Yes No

Not accurate

Not enough depth

Need more code examples

(1500 characters remaining)