J
John Brook
Dear All,
I am trying to create named pipes using VB.NET and calls to kernel32 as
shown on the msdn site.
All appears well with the calls and the returned parameters suggests that
data has been transfered, that is the number of bytes received / transmitted
is as expected but there is no data in the buffers.
I have tried all sorts of buffer types byte, string, ..... to no avail.
Is it to do with the way .NET passes the ref (BYREF) to kernel32.dll as I
have seen some references to different ways the old VB versions handled the
pointers ?
Does anyone know if there is a problem with the way VB.NET calls
kernel32.dll.
I have experienced simillar problems trying to get VB.NET to call the
wrappers for OPC. I spent many days trying to get the calls to work until I
found that there was a problem with VB.net and wrappers.
John.
I am trying to create named pipes using VB.NET and calls to kernel32 as
shown on the msdn site.
All appears well with the calls and the returned parameters suggests that
data has been transfered, that is the number of bytes received / transmitted
is as expected but there is no data in the buffers.
I have tried all sorts of buffer types byte, string, ..... to no avail.
Is it to do with the way .NET passes the ref (BYREF) to kernel32.dll as I
have seen some references to different ways the old VB versions handled the
pointers ?
Does anyone know if there is a problem with the way VB.NET calls
kernel32.dll.
I have experienced simillar problems trying to get VB.NET to call the
wrappers for OPC. I spent many days trying to get the calls to work until I
found that there was a problem with VB.net and wrappers.
John.