Default working directory does not match expectations

[PathogenDavid]

Hello!

When launching a Rust app with this extension, it sets the working directory to the target output path. IE: Launching the project minigrep will launch ...\minigrep\target\debug\minigrep.exe with ...\minigrep\target\debug\ as the working directory.

While I actually personally prefer what your extension is doing, this runs contrary to what I've grown to expect from other Rust tools.

The Rust Book typically has you running cargo run in the context of the same folder as Cargo.toml. Which means the working directory will be that folder. (...\minigrep\ in the example above.)

By default the rust-analyzer extension for VSCode as well as CLion with the JetBrains Rust extension follow this behavior as well -- launching from ...\minigrep\.

Ideally the working directory could be customized as well. I saw #10 but it seems you can't change the working directory with launch.vs.json.

[ericsink]

Hmmm. I'm pretty sure that has annoyed me too. I think it's just the default Visual Studio is giving us, but I'm also pretty sure we can change it. We'll investigate. Thanks.