sync-socket | A synchronous interface to Node 's net.Socket | Socket library

Boost Version : 1.68

C++ Standard : C++17

Development Platform : MSVC 2017

Operating System : Windows 10 Professional

PC Architecture : x64

I am using Boost::Asio to create an asynchronous TCP connection. During first successful connection everything works properly. Due to certain problem it socket break it attempts to re-connect and that time I get the run-time error. Even though I get run-time error the program still is able to receive data.

At first I was attempting to reconnect the socket in my main function's while (infinite) loop (main thread), but I was getting the error. I was getting error in

D:\vcpkg\installed\x64-windows\include\boost\asio\detail\impl\win_iocp_io_context.ipp

Disclaimer: My C# isn't even close to as good as my C++

I am trying to learn how to do async sockets in C# in order to write a test app for a component of mine. My former attempts using TcpClient ended in failure and you can read the outstanding questions on that here:

TcpClient.NetworkStream Async operations - Canceling / Disconnect

Detect errors with NetworkStream.WriteAsync

Since, I could not get that working, I tried using Socket.BeginX and Socket.EndX instead. I got much further along. My problem now is that in the listing below, when it comes time to disconnect, which in turn calls shutdown and close on the socket, async operations are still outstanding and they will throw an object disposed exception or an object is set to null exception.

I found a similar post about that here:

After disposing async socket (.Net) callbacks still get called

However, I do not accept that answer, because if you are using exceptions for intended behavior, then 1) They are not exceptional 2) You cannot tell if the exception was thrown for your intended case or if it was thrown because you actually used a disposed object or a null reference in your async method, other than the socket.

In C++ with async socket code, I'd keep track of the number of outstanding async operations with Interlocked and when it came time to disconnect, I'd call shutdown, then wait for the interlocked to hit 0, and then close and destroy any members I needed to.

How would I go about waiting in my Disconnect method for all outstanding Async operations to complete in C# in the following listing?