> So I tried vagrant VM with virtualbox - and shared folders... so I could keep my windows GUIs without needing to sshing everything to the VM. Somehow - even though the shared folders thing means the VM is ultimately using the windows filesystem
Maybe the other way would be easier, use the VM for all dev file storage as well, and export a SMB share that you can connect to from windows. Same sharing capability (as long as the VM is running), but you don't have to worry about different underlying file system semantics.
> So - I ditched vagrant and shared folders and use a totally contained VM with the ubuntu GUI... it's slow and horrid and it makes me cry... but at least I can alt-tab and waste time in a browser in the windows GUI if I want to.
Personally, I would just SSH for access to the VM though, as I find PuTTY superior to having a desktop as a window on a desktop (I would prefer to RDP to a local Windows VM as well). But I use Vim as my IDE, so it's extremely easy for me to do so.
That said, Visual Studio announced support for targeting Linux today (I assume either through SSH to a local VM or remote box and/or the local Linux support they announced here, so that might be an acceptable route in the future.
Maybe the other way would be easier, use the VM for all dev file storage as well, and export a SMB share that you can connect to from windows. Same sharing capability (as long as the VM is running), but you don't have to worry about different underlying file system semantics.
> So - I ditched vagrant and shared folders and use a totally contained VM with the ubuntu GUI... it's slow and horrid and it makes me cry... but at least I can alt-tab and waste time in a browser in the windows GUI if I want to.
Personally, I would just SSH for access to the VM though, as I find PuTTY superior to having a desktop as a window on a desktop (I would prefer to RDP to a local Windows VM as well). But I use Vim as my IDE, so it's extremely easy for me to do so.
That said, Visual Studio announced support for targeting Linux today (I assume either through SSH to a local VM or remote box and/or the local Linux support they announced here, so that might be an acceptable route in the future.