Re: Can't exit app after BeginReceive
- From: "Paul G. Tobey [eMVP]" <ptobey no spam AT no instrument no spam DOT com>
- Date: Mon, 9 May 2005 15:00:49 -0700
There's a thread being started by that call and the thread isn't exiting. I
don't know what would break it out there, but I'd try calling socket.Close()
before anything else. For better control over what's going on, use your own
thread with blocking calls rather than BeginXXX(), which creates the thread
behind your back.
Paul T.
"Mike" <seattlevine@xxxxxxxxx> wrote in message
news:1115674027.910754.300790@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> I've seen a bit of traffic in this group about similar problems but am
> not quite sure if this is the same. I have an app that needs to read
> asynchronous data over a socket forever, handling it as it comes in.
> The app needs to continue to perform other tasks based on user input.
>
> So, I create a socket, connect it to my serving app (running on the
> same device) and call BeginRecieve. All is working as expected except
> that when I call Application.Exit(), the application does not exit.
> I've tried calling Shutdown() on the socket, but this did not help.
>
> Thanks,
> Mike
>
.
- References:
- Can't exit app after BeginReceive
- From: Mike
- Can't exit app after BeginReceive
- Prev by Date: Re: Full duplex audio with the Waveform Audio Interface
- Next by Date: Re: phone support and poom access
- Previous by thread: Can't exit app after BeginReceive
- Next by thread: Re: Can't exit app after BeginReceive
- Index(es):
Relevant Pages
|
