Are you using TcpClient?

I've extensively use of TcpClient in Monotouch applications and have had no
problems.  The only thing I make sure to do, before calling Close is making
sure the socket is actually connected.  The networking infrastructure I used
was developed on Windows, with the project ported over as a Monotouch
library and recompiled (outputting a DLL), but that shouldn't matter.  My
app allows for many to one, or one to many discovery (UDP/multicast) and one
to one communication (TCP/unicast) and have yet to see an issue with closing
the socket.  Again, though, I'm assuming TcpClient usage.

                    // if the underlying tcp connection is active
                    if (SocketClient.Connected)
                    {
                        // disconnect the underlying connection
                        SocketClient.Close();
                    }



--
View this message in context: 
http://monotouch.2284126.n4.nabble.com/socket-Close-problem-tp4656277p4656278.html
Sent from the MonoTouch mailing list archive at Nabble.com.
_______________________________________________
MonoTouch mailing list
[email protected]
http://lists.ximian.com/mailman/listinfo/monotouch

Reply via email to