title: Wrong gopath when debugging project in VS Code
body: <p>From one day to the next I can't manage to debug a project where everything worked perfectly before.
  I'm sure I haven't changed anything about the project or its settings during this time. All I did was work on another project in the same <strong>IDE (VS Code)</strong>.</p>
  
  <h2>The actual error in VS Code:</h2>
  
  <pre><code>dbInteraction.go:8:2: cannot find package "github.com/go-sql-driver/mysql" in any of:
  C:\Go\src\github.com\go-sql-driver\mysql (from $GOROOT)
  c:\Users\Mani\Documents\Programmier Projekte\PRJCTNAME\src\github.com\go-sql-driver\mysql (from $GOPATH)
  main.go:8:2: cannot find package "github.com/gorilla/mux" in any of:
  C:\Go\src\github.com\gorilla\mux (from $GOROOT)
  c:\Users\Mani\Documents\Programmier Projekte\PRJCTNAME\src\github.com\gorilla\mux (from $GOPATH)
  exit status 1
  Process exiting with code: 1
  </code></pre>
  
  <h2>Checking the environment variables:</h2>
  
  <pre><code>C:\Users\Mani&gt;echo %GOPATH%
  C:\Users\Mani\go
  
  C:\Users\Mani&gt;echo %GOROOT%
  C:\Go\
  </code></pre>
  
  <p>As you can see, my environment variables are set as desired and the $GOPATH in the debug output does not match this path; in contract it is the actual path of my go sources for this project.</p>
  
  <p>When i build the project over the command line with <code>go build</code> (in the project directory) it works perfectly. That gives me the suspicion that VS Code is responsible for the problem.</p>
  
  <p><strong>The user settings and workspace settings in VS Code are both empty. Also empty is the project specific VS-Code <code>settings.go</code> and the <code>launch.go</code> has not changed from the default.</strong></p>
  
  <p><strong>EDIT 1:</strong> If i remember correctly, i think I switched from <code>VS Code 32bit</code> to <code>VS Code 64bit</code> in between.</p>
  
  <p><strong>EDIT 2:</strong> After setting the env parameter in the launch.json I am able to debug the program again but now i <strong><em>do not get any output in the debug console.</em></strong></p>