S
Skybuck Flying
Hello...
Is it to much to ask for that .NET has a list of error messages ? so a
programmer can do something like:
GetErrorMessage( ErrorCode : integer ) : string; !
This text just says it all, it's like: "Here is your stupid error code, now
piss off" Like a kick in the butt lol !
"
Note If this constructor throws a SocketException, use
SocketException.ErrorCode to obtain the specific error code. Once you have
obtained this code, you can refer to the Windows Socket Version 2 API error
code documentation in MSDN for a detailed description of the error.
"
Bye,
Skybuck.
Is it to much to ask for that .NET has a list of error messages ? so a
programmer can do something like:
GetErrorMessage( ErrorCode : integer ) : string; !
This text just says it all, it's like: "Here is your stupid error code, now
piss off" Like a kick in the butt lol !
"
Note If this constructor throws a SocketException, use
SocketException.ErrorCode to obtain the specific error code. Once you have
obtained this code, you can refer to the Windows Socket Version 2 API error
code documentation in MSDN for a detailed description of the error.
"
Bye,
Skybuck.