On Tue, Jul 7, 2009 at 7:00 PM, Commander Pirx
I was struggling with this problem too. Include
before and all works fine. "Robert Jones"
schrieb im Newsbeitrag news:4efd67eb0907070616i225bc2f4h7a4a255be2e8bd5d@mail.gmail.com... On Tue, Jul 7, 2009 at 11:42 AM, Igor R
wrote: What's the deal with Winsock.h & Asio?
I can see there's been chatter on this topic before, but not what the result is.
Could you please mention your Boost version, compiler and the specific issue you encounter?
Yeah, sorry, I thought this would instantly ring bells with folks!
Boost 1.38, Vis Studio 2005, and the issue is that unless I put the main Boost.Asio header first in my #include list I get a failure message
WinSock.h has already been included
from socket_types.hpp.
Thanks, Rob.
I'm not sure what the specific problem is, but this sounds eerily similar to
the issues you encounter when using raw winsock programming without the
presence of asio at all. If it's the problem I'm thinking of, then I'm
pretty sure you can get around it by including