Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Sigh, this an age old problem with USB serial port emulators. Serial ports are devices that date from the stone age. They used to be screwed into the bus, no way to remove them while a program is using it without drawing sparks and billowing smoke. Stone age also includes the lack for any kind of plug-and-play support so that a program could detect that the device is suddenly gonzo.</p> <p>Unfortunately, the majority of the crummy device drivers that emulate them just make them disappear, even though a program has the port opened. This works just about as well as jerking a flash drive out of the socket when Windows is writing files to it. There's a background worker thread that waits for notifications from the device driver so that it can generate the DataReceived, ErrorReceived and PinChanged events. That thread suffers a heart attack when the device suddenly disappears. You can't catch that, it is a thread that was started by the SerialPort class, you can't wrap it with try/catch.</p> <p>By popular demand, Microsoft did something about it in .NET 4.0. Not actually sure what happens in that release. If you're stuck on an earlier release, the only reasonable thing you can do is tape a sign next to the USB slot: "Don't remove while in use!" Which inevitably makes somebody unplug the device at least twice to see what happens. After which they get bored with that and leave you in peace.</p> <p>The very unreasonable workaround is an app.exe.config file with this content:</p> <pre><code>&lt;?xml version ="1.0"?&gt; &lt;configuration&gt; &lt;runtime&gt; &lt;legacyUnhandledExceptionPolicy enabled="1"/&gt; &lt;/runtime&gt; &lt;/configuration&gt; </code></pre> <p>Don't use it.</p>
    singulars
    1. This table or related slice is empty.
    1. POProblem with SerialPort
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USHans Passant
    1. USHans Passant
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POProblem with SerialPort
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COOh, just as I expected...
      singulars
      1. PO
      1. US26071986
    2. COdid they really fix this in 4.0? One day soon I should test it for myself. If so, then all I can say is about time. The bug has been around for a very long time.
      singulars
      1. PO
      1. USdbasnett
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload