>It has been awhile since I wrote an application that used networking with tcp. I am not where I can access it as I am out of town but I think you will want to make your networking function in a seperate assembly and use events to notify back to the application class. This way it won't really matter that it is in a loop to listen. In other words you create your own event to report when data is retrieved. I could probably get you some examples when I get home on Sunday night.
>Tim
>
>>I'm really just started with .NET (mostly for fun :o)
>>I have to listen a TCP port for some data, but I do not want to do this in a loop.
>>What Event I should handle?
>>Every example I found is put the code in a loop (or a very complex async code).
>>In the very old WinSock colntrol there was a DataArival event, where it is in Socket class?
>>
>>I just want this to be an event handled form :-)
>>TIA

This is not a networking application (OK, part of it :-)))
I need to listen our VoiP phone center to get the calling phones and display them on the form.