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

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" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> 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
>

Mike wrote:

> 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.

You may try ExitProcess:

[System.Runtime.InteropServices.DllImport("coredll.dll")]
public static extern void ExitProcess(uint uExitCode);

Rob

I don't think that you want to do that, even if it works. When you have a
problem that is caused by you leaving some resources, a thread in this case,
allocated, the right fix is to deallocate them, not to find a bigger hammer
to exit the process with.

Paul T.

"Robert Jordan" <(E-Mail Removed)> wrote in message
news:d5opa2$ab0$01$(E-Mail Removed)...
> Mike wrote:
>
>> 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.
>
> You may try ExitProcess:
>
> [System.Runtime.InteropServices.DllImport("coredll.dll")]
> public static extern void ExitProcess(uint uExitCode);
>
> Rob

I've tried calling Close after calling Shutdown, as the documentation
says to do, but then I get a System.ObjectDisposedException. I'll give
the direct threading method a try.

Try calling Close() and forgetting about Shutdown().

Paul T.

"Mike" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I've tried calling Close after calling Shutdown, as the documentation
> says to do, but then I get a System.ObjectDisposedException. I'll give
> the direct threading method a try.
>

I had tried all cominations of Shutdown, Close, and EndReceive that I
could think of. I hate to say it (or love to say it) but...

I switched back to my PC from the laptop I was working on, and now
everything is fine (without calling Close, Shutdown, or anything). So
I'll have to chalk this up to user error or a bad insall on my laptop
(using VS2005 beta 2 in both cases).

Thanks for the help.