Hi,
Where the binary of your build is located depends on the project type. If your project is a normal Linux project built on the BeagleBone then the binary is in the build directory on the device, you can see the file transfer path on the project settings page in VisualGDB Project Properties (by default a subdirectory of /tmp/VisualGDB). If you are building the Linux project using a cross-compiler, then the binary is in the project directory on the Windows machine, before debugging the binary is deployed to /tmp. If your project is an Android project producing an apk file, then this also can be found in the project directory on the Windows machine, during deployment it is installed as all other apps on the Android device. Usually VisualGDB does not rename the binaries, only library project outputs and Android apk files have the necessary prefixes and suffixes appended.
The best way to transfer files between the device and the Windows machine depends on the use case. Source files for Linux projects are transferred automatically, if anything else is needed for routine transferring then adding transfer commands to Custom build steps, Custom debug steps and Custom shortcuts in VisualGDB Project Properties is most convenient. If SSH is not possible due to using Android, then make these commands use “adb pull” or “adb push” instead. For one-off transfers you can open an SSH console to the device from Tools->SSH Host Manager and use the SCP menu there.