为什么TcpClient的此代码在vb.net中有效，而在c＃中却无效？

Question

A little experiment here, code that I inherited and plan to refactor, but I'm stumped on one thing. The one in vb.net works, but the one in c# does not.

By the way, BUFFER_SIZE is equal to 2048 , and I know it has several issues, but I can only assume I'm misunderstanding the correlation between Byte constructs with the two languages:

Dim bytesRcvd As Integer = 0
Dim byteSendBuffer As Byte() = New Byte(BUFFER_SIZE - 1) {}
Dim byteReceiveBuffer As Byte() = New Byte(BUFFER_SIZE - 1) {}
Dim receiveMessage As String = Nothing
byteSendBuffer = Encoding.ASCII.GetBytes(sendMessage)
Dim client As System.Net.Sockets.TcpClient = Nothing
Dim netStream As System.Net.Sockets.NetworkStream = Nothing

client = New System.Net.Sockets.TcpClient("localhost", 9060)

netStream = client.GetStream()

netStream.Write(byteSendBuffer, 0, byteSendBuffer.Length)
bytesRcvd = netStream.Read(byteReceiveBuffer, 0, BUFFER_SIZE)
receiveMessage = Encoding.ASCII.GetString(byteReceiveBuffer, 0, bytesRcvd)
netStream.Close()
client.Close()

C#:

int bytesRcvd = 0;
var byteSendBuffer = new Byte[BUFFER_SIZE - 1];
var byteReceiveBuffer = new Byte[BUFFER_SIZE - 1];
string receiveMessage = null;
byteSendBuffer = Encoding.ASCII.GetBytes(sendMessage);
System.Net.Sockets.TcpClient client = null;
System.Net.Sockets.NetworkStream netStream = null;
client = new System.Net.Sockets.TcpClient("localhost", 9060);

netStream = client.GetStream();

netStream.Write(byteSendBuffer, 0, byteSendBuffer.Length);
bytesRcvd = netStream.Read(byteReceiveBuffer, 0, BUFFER_SIZE);

receiveMessage = Encoding.ASCII.GetString(byteReceiveBuffer, 0, bytesRcvd);
netStream.Close();
client.Close();

The error received is:

Specified argument was out of the range of valid values.

This occurs on netStream.read

Ah yes, so Byte is handled differently.. Focusing on the c# version, changing:

var byteSendBuffer = new Byte[BUFFER_SIZE - 1];
var byteReceiveBuffer = new Byte[BUFFER_SIZE - 1];

To this:

var byteSendBuffer = new Byte[BUFFER_SIZE];
var byteReceiveBuffer = new Byte[BUFFER_SIZE];

No error, but netStream.read hangs indefinitely, so apparently not getting any data back, right?

I tried wrapping it all with:

if(netStream.CanRead()) { ... }

Didn't work, still hangs.

Can you spot a reason? Again, yes I'm aware that this is ugly. I'll get to that.

Update

This is absolutely frustrating. I've tried numerous examples of suggested configurations for this. In the new c# (or was) solution, I added a vb project just for TcpClient commands. No matter what else I do, it hangs indefinitely on read , but works with vb .

Final Update

Well, all of this hassle and helpful advice, and it turns this was one of those huge major coincidences dealing with small details, as in the listening service on the other end that I didn't have access to. The procedure to return the messages to be sent to the listener was returning incorrect messages, and the listener was not responding with data, and it just timed out. Such a tiny detail, (like a few characters) that it was hard to spot.

Answer 1

Try this

 bytesRcvd = netStream.Read(byteReceiveBuffer, 0,
 byteReceiveBuffer.Length);

Instead of

bytesRcvd = netStream.Read(byteReceiveBuffer, 0,
     BUFFER_SIZE );

your byteReceiveBuffer length is is 2047 and BUFFER_SIZE is 2048