.NET (Core and Framework)

Private Sub ReceiveMessages()
        Try
            ThreadReceive = New System.Threading.Thread(AddressOf ReceiverMethod)
            ThreadReceive.Start()
        Catch ex As System.Threading.ThreadAbortException
            ' this generally means that the thread was deliberately aborted, so we can ignore it
        Catch e As Exception
            If Not ShuttingDown Then Throw New ApplicationException("Problem receiving data from Thermostat" & vbCrLf, e)
        End Try
End Sub

Private Sub ReceiverMethod()
    While Not ShuttingDown
        Try   
            Dim receiveBytes As [Byte]() = TCudpClient.Receive(RecEndpoint)
        ' Some error checking code omitted
            Process_Heartbeat(receiveBytes)

            If NewSettings Then ' There are some queued commands
                UpDating = True ' Set a flag to prevent new commands being added while we are processing existing ones
                Send_Commands() ' See below
                UpDating = False
                NewSettings = False
            End If
        Catch ex As System.Threading.ThreadAbortException
            ' this generally means that the thread was deliberately aborted, so we can ignore it
        Catch e As Exception
            If Not ShuttingDown Then Throw New ApplicationException("Problem receiving data from Thermostat" & vbCrLf, e)
        End Try
    End While
End Sub

For Each tc In ThermostatCommands ' find the first available command
   If tc.Pending Then
        System.Threading.Thread.Sleep(100)
        SendMessage(tc.ComBuff) ' See below
         System.Threading.Thread.Sleep(100)
        SendMessage(tc.ComBuff) ' See below
        tc.ComBuff = Nothing
        tc.Pending = False
        Exit For
    End If
Next

foreach (Process p in Process.GetProcesses())
           {
             string procFile;
              try
               {
                  procFile = p.Modules[0].FileName; // Get the full Path to modules
               }
               catch (Win32Exception ex)
               {
                   procFile = ex.Message;

               }
               listBox1.Items.Add(string.Format("Process {0}: {1}", p.ProcessName, procFile));
           }

Luc Pattyn wrote:

you can have as many pumps as you like.

Luc Pattyn wrote:

a dialog, it has its own message pump

Spectre_001 wrote:

Windows under the hood is still basicaly a non-preemptive multitasking OS

Guy Harwood wrote:

*shudders at recollection of coding in access*

MessagePump()
{
   while ( true )
   {
      Message msg = GetMessage();  // Get the next message from the queue
      DispatchMessage( msg );  // This will do the work
      if ( msg.Msg == WM_QUIT ) break;
   }
}

Application.Run
MessagePump
DispatchMessage
... framework stuff ...
Timer1.TimerEvent
SomeForm.ShowDialog
Application.DoEvents
MessagePump
DispatchMessage
... framework stuff ...
Timer1.TimerEvent
SomeForm.ShowDialog   <-- if you indeed do this call then this will repeat until...

   MessagePump()
   {
      while ( true )
      {
Adr 1    Message msg = GetMessage();  // Get the next message from the queue
Adr 2    DispatchMessage( msg );  // This will do the work
Adr 3    if ( msg.Msg == WM_QUIT ) break;
      }
   }