Visual Studio on VM - Shared Folder Permission Problems

Is anyone else using Virtualbox on their Mac to run Visual Studio (2008 express) on a virtual machine? I am following the guide on the wiki and comments in the forums for using a VM . Everything works great except when I open the solution in Visual Studio I get this warning:

“The project location is not trusted: [path] Running the application may result in security exceptions when it attempts to perform actions which require full trust.”

I can still open the solution and add/delete files, but if I edit a file I cannot save. I know it’s not a straight file permission issue because I can actually edit files on the share using notepad or any other program for that matter. I’m assuming it is the painfully convoluted .NET permission system that is causing problems. Did some searches online and it seems like I need to setup my shares to be fully trusted:

Seems simple enough, except after following those instructions it still does not work (tried a reboot to be safe).

Here are the commands I have tried of have tried from the 2.0* .NET Framework folder (Visual Studio runs off 3.5/3.0/2.0 framework even though Unity is only targeting 1.1):

  • Where Desktop is the share name I made and VBOXSVR is the machine name Virtualbox uses for its file shares
    caspol -m -ag 1.2 -url file://\VBOXSVR\Desktop* FullTrust
    caspol -m -ag 1.2 -url file://\VBOXSVR* FullTrust
    caspol -m -ag 1.2 -url \VBOXSVR\Desktop* FullTrust
    caspol -m -ag 1.2 -url \VBOXSVR* FullTrust

I also tried using the Framework Configuration Tool under Administration Tools and gave every code group Full Trust. This allowed me to open the solution without a warning, but it still fails if I edit a file and try to save it.

Finally I tried creating a project on the VMs drive and added a file from the folder share as a linked item. No security warning when starting (as I would expect), but still cannot save the linked file if I edit it.

Has anyone else had this problem? I’ll probably download a demo of VMWare or Parallels tonight and see if I have the same issue.

Thanks,
Dash

Got it working. I set up an SMB share in OS X instead of using the Virtualbox shared folders. Still not sure why the vbox shares didn’t work or if they would have performed better.