Debug is the same for all chips. Are you using serial/usb upload or OTA?

If serial/usb then ensure the toolbar says Debug and not Release

note: If you are debugging using the upload port you do not need to configure the Debugger menu properties such as local port.

The issue might be your usb driver. That driver is confusing because the version 10 for windows universal does not work for normal windows 10 c# code which is what visual micro uses to access the port. You should ensure you have the last v6x version of that driver installed. You are not using windows universal so that is why the 10x is wrong for you.

Please test your serial connection using a new empty project with little code. When the serial works the visual micro debugger should work.

If the debugger does not work after that then let me know

Hi,

Code size does not affect the debugger. 

It is a simple debugger that does not support stepping but supports charting, performance monitor and other features. Pls see the debugger docs and the debug overview.

Please test serial.println() in your large project to see if it is working. If so at what speed? Does 115200 work?

Thanks

I didn't see the loop(void) in your first example. Normally for arduino it is just loop()

If you also have a setup(void) that might cause the debug to fail to start.

void setup()
{

} 

Yes jtag is coming over the next few months and will loose support for vs2012 and vs2013. vs2019 1.2+ requires some changes and it seems like the right time to be able to take advantage of never microsoft gdb technologies.