App Development on Windows guest

[jsimmonstx]

I'm on Linux Mint 19
Using VirtualBox 5.2.22 r126460
Guest is Windows 7

I'm trying to use Visual Studio 2017 on the Windows guest. The project files exist on a host share. I can write and compile code, but when I try to run it, I get an error saying:

Error while trying to run project: Unable to start program ""\\Mars\nvme\dev\solutionfolder\projectfolder\bin\Debug\app.exe".
Access is denied.

I'm pretty this isn't a VB problem, but since it's a VB Windows guest, I was wondering if anyone could give me some guidance.

[socratis]

The project files exist on a host share.

Windows share, or VirtualBox Shared Folder?

I'm pretty this isn't a VB problem

It is an issue because of the combination of networked folders and the UAC mechanism in Windows. Here's a small part of a larger article (that I've never polished enough to post) that was dealing with the issue:

---

Notes

• If you run "<TheProgram>.exe" from a VirtualBox share that is not mapped (does not a drive letter assigned), you get the following error:

  Unable to assign a drive letter
  to the script path \\VBoxSvr\Share\sub

• If you run "<TheProgram>.exe" from a VirtualBox share that is mapped (has a drive letter assigned), you get the following error:

  W:\Share\<TheProgram>.exe
  The specified path does not exist.
  Check the path and then try again.

Solutions

1. Disable UAC control temporarily. Then run "<TheProgram>.exe" from a mapped share. You can turn off the network if you don't feel protected enough.
2. Copy the whole "Share\Sub" sub-directory in the VM and run "<TheProgram>.exe" from there.

Explanation

• When a user connects to a network share, Windows tries to connect with two sets of credentials. This fails due to the UAC control. It is so by design. For references and further reading on previous reports and the reasoning behind it (read especially the Microsoft links):
  • https://www.google.gr/search?q=the+spec ... ualbox.org
  • viewtopic.php?f=7&t=48570
  • viewtopic.php?f=7&t=40036
  • https://www.virtualbox.org/ticket/5732
  • https://support.microsoft.com/en-us/kb/303308
  • https://support.microsoft.com/en-us/kb/2019185