Click here to Skip to main content
15,891,375 members

Comments by pdoxtader (Top 135 by date)

pdoxtader 3 days ago View    
Well, when I was at Microsoft we weren't using TAP yet. But I CAN tell you that they're just humans like you and me - not supermen or gods. So they're using TAP in .net core? Wonderful. I never said it was evil, and I'm not arguing that it shouldn't be used. They're just people - They embrace and abandon coding patterns as they need to - just like they build and abandon UI widget frameworks when they realize that something better has come along, and they want to pursue that. Do you know how many cool and interesting things they have there that never saw the light of day?

All I said was that it's valuable to LEARN about threading, locks, synchronization, etc. FIRST. You don't agree? Fine. You do you. I think people should understand it.
pdoxtader 3 days ago View    
I think we'll have to agree to disagree on TAP "removing most of the complexity". You still need to understand threading, locks, data synchronization, etc. Starting with Thread and learning about threading first is still the right thing to do - and that's what I was hoping would happen here.
pdoxtader 3 days ago View    
I'm aware. I was just trying to be as clear as possible, and it's easier to show how threading works this way then to explain TAP. And clearly, there is blocking happening on the UI thread. If there wasn't, the UI would be updating.
pdoxtader 31-Mar-23 12:12pm View    
The paint event is the standard place to do your graphics / drawing in winforms. When I do that kind of thing, it goes in the paint event. You'll trigger updates to your panel using .Refresh() or Invalidate(), depending. You may need to create some drawing operation objects and add them to a list that gets enumerated and executed during paint.
pdoxtader 22-Aug-21 23:00pm View    
You aren't giving us enough information to answer that, because we can't see your code. From the error you are showing us, it looks like you aren't actually creating a new socket in your Connect() method, and are actually attempting to connect using the same socket. Troubleshooting this is pretty basic, and if you're having trouble with it then maybe you need to get more comfortable using the debugger in visual studio before attempting to tackle a more complicated subject like TCP/IP communications.