Hi, 

If you have a lot of your own serial please use visual micro in release mode to test the serial monitor and upload is working well before using debug mode.

What is the DTR and RTS of your serial monitor set to? They are ON by default and should be ON.

What board options are set in Arduino and what are set in Visual Micro?

What is the name of the usb driver that teensy is using? You can see this in device manager. I ask because there can be a difference between the arduino java access of serial v's Visual Micro windows.

Please switch off auto-reconnect on the serial monitor and leave it open and connected. The build and upload.

Does that have different effect?

Also:   

Just opened a generic serial term app window (RealTerm) and the messages are were appearing perfectly fine and instantly. 
Closed the term app.  Restarted VS/VM, suddenly the port is appearing/working. 


Its like the other apps do some kind of port init but VS/VM doesnt?

Tim@Visual Micro wrote on Jun 27^th, 2019 at 12:16pm:


Well just FYI I have pretty clearly posted all the versions I am using right from the start ^^^ as I always do, but I see the new release just came out so I updated to:
1906.26.0 as of this morning. 

No change. 

Tim@Visual Micro wrote on Jun 27^th, 2019 at 12:16pm:


Done.  I had tried that both ways in past, but... nonetheless, done, and, no change. 

Tim@Visual Micro wrote on Jun 27^th, 2019 at 12:16pm:


Done again (as noted here I have been trying that per previouis instructions already and have noted the results...)

Tim@Visual Micro wrote on Jun 27^th, 2019 at 12:16pm:


No change. 

Tim@Visual Micro wrote on Jun 27^th, 2019 at 12:16pm:


Done. Emailing 

Tim@Visual Micro wrote on Jun 27^th, 2019 at 12:16pm:


usbser.sys
v.10.0.17763.1
6/21/2006

"Driver Management concluded the process to install driver usbser.inf_amd64_106c37dc8954b06b for Device Instance ID USB\VID_16C0&PID_0483\3267220 with the following status: 0x0."


Other notes:

I have also tried "Reset These Settings" under debugger to no effect. 

Have tried "Debug Settings" both Off and Debug:Serial to no effect. 

I have reverted for this testing purpose to an extremely simplified sketch with no interrupts enabled, and barely any lines of code aside from reading some joystick pins and printing to Serial.  So there should be no conflicts anywhere in the code.  I will attach the sketch as well although its about as short a sketch as you can write. 

The output continues to appear no problem on any other program that opens COM6 on this computer - Arduino, RealTerm, etc. so the port is working perfectly fine, there's just some issue w/ how VM is trying to open it.  

I sometimes get "Port open" message in the Port window, but sometimes/often it remains completely blank.  With the last run sent by email I got these messages after attempting to load it a couple of times. 

Quote:

Tim@Visual Micro wrote on Jun 27^th, 2019 at 2:39pm:


There are no silly questions at this point!

Yes.  Using a hub.  I will try both of those things.  I suppose I could write my own C# console app and check that too, but let me try the basic serial port stuff and see what happens.   

I did once have a Netduino that was bizarre about which USB ports it preferred but the hub/port I use now has been generally rock solid but... who knows... 

Ah well done, thanks for all the good reporting.

VS isn't involved, this is windows getting it's knickers in a twist when using the Microsoft System.IO.SerialPorts namespace instead of using underlying win32 calls for the port management. Hopefully it only happens once or twice in a life time. Sometimes powering off (then restarting) the pc and all hubs can also resolve port issues.

Having said that never seen this combination before.

Sorry for the delay. The latest release 1907.6.7 resolves the issue which was related to the recent conversion to asnyc packages for VS2019 (vs2017 uses same vm code so was also affected).