- Notifications
You must be signed in to change notification settings - Fork70
Visual Studio extension for Rust
License
MIT, Unknown licenses found
Licenses found
PistonDevelopers/VisualRust
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
Currently in development, and not feature complete. Stable versions areavailableon the Visual Studio extension gallery.
Unstable, but more recent builds are downloadable fromAppVeyor (choose "Configuration:Release" and "Artifacts").
- Project support based on Cargo
- Syntax highlighting
- Autocomplete
- Go to definition
- Debugging for both MSVC and GNU toolchains
- Conditional breakpoints
- Watch window (with the ability to change the runtime state)
- Immediate window (with the ability to change the runtime state)
- Set next statement
- Call stack view and navigation
Feel free to open issues, post comments about progress, questions, new ideas,brain storming etc. You can remove and edit comments as a way of refining ideasin the issue tracker. This is very helpful because many concerns in thisproject are very complex. Many issues needs to be broken down into newissues before they can be implemented.
Issues markedReady represent tasks that have a clear design anddeliverables. They are recommended starting points if you don'twant to spend time discussing and evaluating implementation.
Issues markedInformation require some wider perspective and discussion.They are perfect if you want to have an impact on the project but don't havethe time to spend coding.
- Fork the main repository
- Work on a feature in your own private branch
- Once you are finished with you work or want someone to you, open a pullrequest
- Someone will review your code and merge it. Some fixes might be required onyour side.
To build this, you'll need Visual Studio 2015 and matchingVisual Studio SDK forthe VS plugin,WiX Toolset 3.10 or higher for the setupproject andJava RE.NuGet will take care of the rest.
If you plan to hack on Visual Rust you should understand difference betweenour two build configurations.
For the
Release
configuration the main project isVisualRust.Setup
,its output is a .msi file that consists of two parts:- MSBuild integration: this lets you build Rust projects (.rsproj) fromthe command line and Visual Studio.
- Visual Studio plugin(s): this adds support for Rust projects (.rsproj)inside Visual Studio. Syntax highlighting, project system, item templates.Everything except building.
For the
Debug
build main project is called simplyVisualRust
and it buildsVisualRust.vsix
which is a VS plugin in a format that is suitable forlocal installation and debugging.It doesn't contain MSBuild integration
Consequently, for the debug build you'll want to either install just MSBuildintegration from the .msi file or build it yourself (VisualRust.Build
) andcopy to%ProgramFiles(x86)%\MSBuild\VisualRust
.
Also you'll want to modifyVisualRust
project with location of yourVisual Studio installation tolaunch it automatically when debugging.
This project is currently maintained byvosen.
Feel free to mail him or ask around in#rust-gamedev
on irc.mozilla.org.
Same as Rust, dual MIT/ASL2. Any contributions made are under this license.
About
Visual Studio extension for Rust
Resources
License
MIT, Unknown licenses found
Licenses found
Uh oh!
There was an error while loading.Please reload this page.
Stars
Watchers
Forks
Packages0
Uh oh!
There was an error while loading.Please reload this page.
Contributors14
Uh oh!
There was an error while loading.Please reload this page.