BUG: The LocalEndPoint property of the Socket class is not set when a new Socket object is returned from an Accept call in Visual Studio .NET 2002 (321087)
The information in this article applies to:
- Microsoft Visual Studio .NET (2002), Professional Edition
This article was previously published under Q321087 SYMPTOMSIn Microsoft Visual Studio .NET 2002, the .NET Socket class has a LocalEndPoint property that is represented by an IP
address and a port number to which the socket is bound. The LocalEndPoint
property is set for a socket object under the following scenarios:
- When a socket object calls bind on the server side.
- When a new socket object is returned from an accept call on the server side.
- When your socket object calls connect on the client side.
However, the new socket object that is returned from an accept call (second bulleted item in the preceding list) may not have
its LocalEndPoint property set correctly. Instead, the LocalEndPoint property
may have its value set to null. STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
This bug was corrected in Visual Studio .NET
2003.
| Modification Type: | Major | Last Reviewed: | 9/19/2005 |
|---|
| Keywords: | kbvs2002sp1sweep kbDSWNET2003Swept kbbug kbenv kbnofix kbpending KB321087 |
|---|
|