I am trying to use VM in Visual Studio.  I want to debug and build arduino IDE projects for the esp-32.

My first project builds but does not download or debug.  I believe the JTAG is properly connected and will download and debug as it works in VisualGDB (cannot import ino).   

I have attached build output as requested.
I have attached a jpg of my VS screen
I have attached a jpg of a screen from your video

My screen is significantly different.
1) mine has a VS menu bar that says release arm64.  This bar does not appear in the video and, at the least is distracting when using VisMicro.
2) my secreen only has 2 VisMicro tool bars, video has 3.  How do I get the layout seen in the video.
3) the video shows debugger set as ESP-Prog which is what I want.  The only options I have are  Disabled, FTDI Adapter
and ESP USB Bridge.  None of these work

Both Visual GDB and VisMicro use same driver install using zadig-2.8

How do I make this work?

Thanks for replying.  The framework is set to Arduino 2, the board is ESP32 Dev Module, the comm port is set to 10.  !0 is the 0 port of the ESP-Prog JTAG interface.  I have searched and can find no way to get the gdb log on VS.  There are lots of methods for Linux but nothing for VS

I can compile, load and debug programs with Visual GDB using the ESP-prog (but no arduino progs.)  That eliminates a lot of possible errors.  I do not know where to go with Visual Micro.

At this point I am stopped.

Thanks

i do not like to be rude but you are not listening.  I am on a trial but will buy if I can do what I need to do.  I spent 3 hours last night in a fruitless effort to make this work.

1) correct drivers have been repeatedly installed using Ziadig.
2) THIS WORKS IN VISUAL GDB but they do not support arduino
3) THE VIDEO from you shows selection of ESP-Prog in the jtag interface board selection.  I do not get this option.
4) Why are you using outdated versions of the Arduino IDE and expressif tools?
5) HAVE YOU LOOKED AT THE PICTURES I SENT WITH MY FIRST POST (PDF) WHICH SHOWS MY VISUAL STUDIO DISPLAY AND THE ONE SEEN ON YOUR VIDEO????

I AM NOW TRYING TO GET THIS WORKING ON PLATFORMIO (VSCODE ugh) AND ON VISUAL GDB.  UNTIL YOU GIVE ME A SOMETHING TO TRY THAT ADDRESS THIS ISSUE,  THAT IS WHERE MY EFFORT WILL GO.  

Yes I am shouting.  You are not doing your job!  My work currently depends on it!!!!!!!

Perhaps you should elevate to someone who knows more about YOUR product

You are on the verge of losing a sale.  I work hard and poor technical support only costs me time I do not have.  This support really is a negative for your product

this was not set.  It is now.  I gets farther but still has an issue.  I have attached the new log.  I attempted to fix this error by reinstalling the driver with zidig.  Now by ports are not showing as they did before.  This has happened to be before.  It is very hard to completely wipe these drivers and start over pnputil even run in admin mode fails.  I have notes from last time I did it but it is difficult.  I am going to work on that.  I have a backup of my drivers but getting windows to allow the overwrite is more than a pain

This is not your area but if you have any ideas, they would be appreciated.

Anyway attached is new log.

I have been off for a while.  Crashed my computer and had to restore from backup

Still not finding JTAG but getting farther.   
  1) build log attached
  2)Zadig log attached
  3)Zip of Zadig created driver files

Only the WinUSB Driver should be used in Zadig (the others will not work).

Interface1 of the ESP-PROG will show as the FTDI driver in Device Manager, as this is the Serial Passthrough port, and will appear under the COM Ports section.

Interface0 of the ESP-PROG will show as the WinUSB driver in Device Manager (once installed), and will appear under the Universal Serial Bus Devices section in Device Manager, as Dual RS232-HS.

From your log the driver has now been installed correctly, as the error about not being able to locate the VID/PID has vanished.

The current error shows there is an issue in the connection between the ESP-PROG and the ESP32 board.  This could be:
1) ESP32 board is not powered (power LED on ESP32 should be on if it is powered)
2) Connection wiring between the ESP32 and ESP-PROG is not fully connected, or connections are imperfect
3) The code currently on the board uses any of the JTAG pins in any way (GPIO12-15)

NOTE: The wiring between the ESP-PROG and ESP32 is sensitive to any connection issue and interference, so it is best to keep these wires as short as possible, and if possible try replacing them with new tight fitting jumper wires (I had the same issue this morning due to loose fitting wires).

If you email us your license key we can review an extension.

In your initial PDF you are using the blink example with GPIO13 in use.  If this is no on the board it will interfere with the JTAG functionality until a sketch is uploaded over serial without GPIO12-15 being used (e.g. change it to pin 17 in the sketch, then perform a serial upload).

Could you try it with VisualGDB to confirm the wiring is correct (and no other interference/noise issues), as this works correctly for us when using an ESP-PROG with an ESP32-WROOM-32D on an ESP32_Devkitc_v4 board.