I have the following issues with compiling code on a windows guest running 
on a linux host:

1. Building with visual studio (msbuild) doesn't work unless you have a 
"proper" login session, which key-based auth to the cygwin ssh server 
doesn't give you 
(see 
http://ilostmynotes.blogspot.com/2015/03/solved-fatal-error-c1902-program.html)

2. I can't just use password auth because vagrant doesn't let you do 
"vagrant ssh -c" when using password auth.  My guess is that this is 
intended to stop people exposing their passwords, but it's an annoying 
behavior I'd like to override since my password is "vagrant" anyway.

3. So I can fallback on using winrm to run msbuild and build things, but 
AFAICT winrm is only available at provisioning time?  So I need to put the 
code that builds stuff in the provisioning script and run --provision and 
reboot the VM (which takes ages) just to rebuild the software.  And I can't 
separate out provisioning and building code :(

It feels like I'm missing something here, particularly #3 seems...wrong.

I think my ideal solution would be if I could override the behavior in #2 
and just use password auth to run over ssh.

My vagrantfile looks like this:

  config.vm.define "windows_7_64" do |box|
    box.vm.synced_folder "../../", "/host"
    box.vm.box = "windows_7_64"
    box.vm.guest = :windows
    # Random keypair generation and insertion doesn't work on Windows
    box.ssh.insert_key = false
    box.vm.communicator = "winrm"
    config.vm.provision "shell", path: "build_windows_templates.bat"
  end

-- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to