Also, if using VS2017, you may also have to set the env var `VisualStudioVersion` to `15.0` to get some cmake-using crates (libssh2-sys, etc) to build. See <a href="https://github.com/alexcrichton/cmake-rs/pull/16#issuecomment-285932296" rel="nofollow">https://github.com/alexcrichton/cmake-rs/pull/16#issuecommen...</a><p>(Note that 15.0 == VS2017, not VS2015)
I recently switched to using Windows full-time. It started off using the Linux subsystem, but then I accidentally trashed it. So I'm now using native Windows. Powershell is surprisingly easy to adapt to, and while I still use vim often, I've been enjoying occasional use of VS: Code.<p>Most stuff Just Works, but there are still some rough edges. A lot of them are simply "I'm not used to the Windows Way" yet instead of Rust problems, though.
Thanks. I made a complementary guide to use the visual studio build tools 2017.
<a href="http://lustysociety.org/programming/how_to_rust_language_visual_studio_2017_windows_10" rel="nofollow">http://lustysociety.org/programming/how_to_rust_language_vis...</a>
It's way too hard to get anything that requires OpenSSL to work, I decided not to write Rust code on my windows PC because of that. I remember the process of just getting it to work as really painful and time consuming.
Other than that I really enjoy writing rust code on my Linux machine.
Visual Studio Code has a pretty decent Rust extension: <a href="https://marketplace.visualstudio.com/items?itemName=kalitaalexey.vscode-rust" rel="nofollow">https://marketplace.visualstudio.com/items?itemName=kalitaal...</a>
Does is also work with the Free-Software MinGW toolchain?<p>That would make it possible to generate Windows binaries without having to run a Windows VM, through cross-compiling, using e.g. MXE: <a href="http://mxe.cc/" rel="nofollow">http://mxe.cc/</a>
Been working with Rust on Windows for almost a year now.<p>My go-to is VSCode + Rust plugin. You get the same debugging as VS2015 via C++ plugin(they both use the same backend). Only time I need to drop over to MSVC is if I need data breakpoints or look at disassembly(usually when I'm dealing with a C library that's misbehaving).<p>VSCode rust plugin gets you racer, rustfmt and a bunch of other goodies(cargo test/check right in the IDE).
I should really find some time to upgrade to VS2017, my understanding is it's a bit faster than VS2015, not just the install. Can anyone comment on this, I always found VS to be a beast, even on an SSD, HDDs being nearly unbearable.<p>I really do like VS Code though... looks like there's some work going there.
Instead of VS try out IntelliJ IDEA with Rust plugin: <a href="https://intellij-rust.github.io" rel="nofollow">https://intellij-rust.github.io</a><p>It gives you the comfort features known from the IntelliJ platform and doesn't add phonehome telemetry to your exe files (like VS2k15).
I personally prefer lxss. While it has some limitations, I am yet to face issues with rust projects. You can also use Intellij-based IDEs with a rust plugin and run `bash` in the command prompt accompanying the IDE. It feels like working on Linux ^_^
Is VisualRust still active?
It seems dead or moving very slowly.
I know there's some commits going into the project, but their last release was over a year ago.