Codeunit 3009 "DotNet_MemoryStream"
Base Application · System.IO
Across versions
- BC23-27present
- BC28declaration changed
- BC29-30unchanged
Neighbourhood 2 connected objects and pages
Base Application · System.IO · BC23-30 · source at ea08af5e · facts from BC29
Procedures
MemoryStream()MemoryStream(var DotNet_Array: Codeunit DotNet_Array)ToArray(var DotNet_Array: Codeunit DotNet_Array)WriteTo(var OutStream: OutStream)Close()CopyFromInStream(var InStream: InStream)GetDotNetStream(var DotNet_Stream: Codeunit DotNet_Stream)SetPosition(NewPosition: Integer)GetMemoryStream(var DotNetMemoryStream2: DotNet MemoryStream)SetMemoryStream(DotNetMemoryStream2: DotNet MemoryStream)
Triggers
OnRun
Calls
From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.
- Codeunit 3000 “DotNet_Array” (1 call:
ToArray → SetArray) - Codeunit 3034 “DotNet_Stream” (1 call:
GetDotNetStream → SetStream)
Ask your agent
Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "codeunit", object_name: "DotNet_MemoryStream"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.