Tooling

Development tools for C#, C++, and Rust

1. Prologue

In this chapter we look at processes for building programs and software systems using C#, C++, and Rust. The intent is to provide build processes for each of the three languages that are as nearly identical as practical, and to enable builds on both Windows and Linux.

One major ingredient is to use Visual Studio Code as a code editor for all three languages on both OS platforms. VS Code supports plugins for each of these languages that provide intellisense and error flags. It also provides a contained terminal window we will use to initiate builds from the command line and executions of successful build products.

2. Visual Studio Code Editor:

Figure 1. VS Code IDE

Installation:

Download Visual Studio Code, a.k.a. VS Code. This works for Windows, Linux, and macOS. Then run installer from Downloads folder.

IDE Setup:

There are two things you may wish to change in the default configuration:

The terminal panel, Figure 1 on the right, is placed by default at the bottom of the IDE window. It works better for me to have in on the right. You can place it wherever you like with settings (click Gear icon at left bottom -> settings):
Settings -> User -> Workbench -> Panel Default Location
By default the IDE shows a code Minimap on the right of the code editing panel. You can disable that with:
Settings -> User -> TextEditor -> Minimap

You will find it convenient to use the key board shortcuts:

"ctrl /" to toggle comments on selected lines
"ctrl [ and ctrl ]" to control indenting of selected lines
Also, to open integrated terminal in any folder, right click any file in the folder and select "Open in Integrated Terminal". This is particularly useful when you open a workspace folder (any folder with .vscode subfolder).

Other Settings:

To change other settings:

"settings -> Editor -> uncheck Accept Suggestion on Commit Character" to avoid many spurious insertions of unwanted suggestions.
"settings -> search for menu -> select Menu Bar Visibility" to show/hide top menu
"F11" to toggle full screen mode
"View -> Command Palette -> .Net: Generate Assets for Build and Debug" enables Run -> Start Debugging. Have to have editor open in project directory.
"ctrl K, ctrl T -> select editor theme" to select one of many alternatives
"settings -> workbench -> appearance -> color customizations" to set terminal colors
"File -> Preferences -> Settings" to change lots of defaults
"File -> Preferences -> Settings -> user -> Features -> Terminal" to change Terminal defaults
"View -> Command Pallet -> Preferences: Open Settings (JSON)" to edit any user setting you've changed

Settings Details

Figure 4. VS Code Project launch Settings

Figure 5. VS Code User Settings

The settings you will manage most often are local settings for each project, found in a .vscode folder at the top level of your project. Initially that folder doesn't exist, and you don't need to explicitly create it. VS Code creates it for you the first time you click on the Run or Terminal -> Run Task menus. You will be asked if you want to configure and, when you affirm by selecting a configuration, the folder is created and populated.

That will happen as long as you have selected one or more plugins (see below). The C#, C++, and Rust plugins supply configurations for debugging. You can then edit them if you wish to modify the way debugging or builds happen.

I do all builds in the terminal, so only have a launch.json file, no tasks.json file for building.

VS Code settings are stored in three places:

local project settings:
Debugging settings in launch.json and build settings in tasks.json

Find in project's .vscode folder, as JSON files launch.json and tasks.json

Access by opening json file in code editor
user settings:
Hundreds of settings for Terminal, Keyboard mappings, ...

Find in C:\Users\[userid]\AppData\Roaming\Code\User\settings.json

Access: View -> Command Pallet -> Preferences -> Open Settings(JSON)
default settings:
All available settings (most of which you don't want to change)

Doesn't appear to be a physical json file.

Access: View -> Command Pallet -> Preferences -> Open Default Settings(JSON)

You can get to forms for changing preferences from Manage icon (gear) at left bottom of IDE.

Setup for Editing, Building, and Debugging Code:

VS Code, as delivered has a very good code editor, but does not have the ability to build, execute, and debug code for the languages of interest to us here. You get those by adding plugins from the plugin selector on the left.

Figure 2. VS Code Plugins

If you click on the plugins icon on the left border of the IDE you will see something like the view shown in Figure 2. That shows that I have installed plugins for C++, C#, CMake, and Rust.

The C++ plugin provides intellisense for the code view and for building and debugging. The plugin uses MsBuild, but the path to that needs to be configured, and you can't easily configure the terminal to use MsBuild if it isn't on your path.

For that, CMake is an excellent alternative. You may wish to look at my CMakeDemo repository for a use example.

You build the project target by running CMake in the attached terminal. Then run or debug using the Run menu at the top of the IDE.

The C# plugin provides intellisense. You need to build your project target in the attached terminal by issuing a "dotnet build" command. Then you can run or debug using the Run menu.

The Rust plugin provides intellisense and the ability to build and run the resulting executable from the Run menu. Usually I do all the building in the terminal window and run from there as well. I just use the VS Code run menu to start Rust debugging.

Debugging:

Figure 3. VS Code Debugging

One final remark: you get finer control over the debugging process by selecting the debug option on the left border of the IDE, just above the plugin selector.

That allows you to select one of multiple debug configurations if you have them defined in launch.json (you find that inside the .vscode folder). You also can view local variables, set watches, and look at machine registers.

If you expand Figure 3. by clicking on the image body, you will see the debug control bar at the top which provides controls for single stepping, step-into, step-outof, restart, and quit.

The first button on the control bar is a continue button that will move to the next available breakpoint. You set those by clicking in the left margin of the edit window, just to the left of the line numbers.

Platforms:

All of the above works almost identically on both Windows and Linux. I've used VS Code on macOS, but haven't yet done much development there, but expect that all of these observations carry over to that platform as well.

Complementing all of this with a github account makes it easy to move code between platforms, and use virtually the same development processes on each.

3. Development Process:

Topic	C#	C++	Rust
Installation	dotnet Download dotnet core latest SDK and Desktop Runtime. Run installer from Downloads directory. The download page has links for Windows, Linux, and macOS.	CMake, C++ tools Download CMake. For Windows, if you have Visual Studio Community Edition you already have the tools you need. For Linux download gcc/g++ from your connected repositories. On Ubuntu, install build-essential for a late version.	Rust: cargo, rustc, clippy Download Rust. That includes rustc, the rust compiler, cargo, a package manager, and other tools like clippy. This works for Windows and Linux.
Work Flow	C# In VS Code navigate to the parent folder where you want to create a dotnet project. Open the terminal (ctrl `) and issue the commands: dotnet new console --name pjname cd pjname That navigates into the new project directory. Now issue the command: dotnet run See the console project build and run, printing "Hello World!" Now you can run the debugger by clicking on the top Run menu, select .net core launch, and step through the code. Results are, by default, shown in the integrated terminal, but you can change that to an external terminal if you wish by editing launch.json in the .vscode folder. Start editing, adding files, and debugging to implement your design.	C++ In VS Code, open the parent folder where you want to create a new C++ project. In the terminal issue the command: mkdir TestDir to create a new directory From the File menu open the new directory and add a new file test.cpp Open the file and add some C++ code in the editor. Now add a CMakeTests.txt file. Initially you may wish to simply copy from the CMakeDemo repository. Create a build directory: mkdir build and cd into that folder in the terminal. Issue the commands: CMake .. CMake ../build . That initializes CMake for this project and then builds it. The result, test.exe will be in /build/debug. Now you can run or start debugging. Here's a couple of nice, brief, CMake tutorials: Build Cmake-based Project CMake Scripting	Rust In VS Code, open the parent folder where you want to create a new Rust project. In the terminal issue the command: cargo new TestPkg That creates a new directory TestPkg with a cargo.toml metadata file and /src folder with hello world Rust code in main.rs. Now you can open the new folder from the File menu and run or start debugging. when you don't need to debug just issue the command: cargo run TestPkg in the terminal. You create a library with the terminal command: cargo new --lib TestLib cargo builds the library starter code with test fixtures for unit tests. Once you have some library code and corresponding tests, you run tests with the terminal command: cargo test If you manually create an /examples folder as a sibling to the /src folder, you can put demonstration code that uses the library and displays results on the termianl. To do that use the command: cargo run --example test1 where test1.rs is the demonstration code inside /examples.

4. Epilogue

The following pages provide sequences of code examples for idioms and principles in each of the three languages cited here, e.g. C#, C++, and Rust. Object model differences will often be pointed out in comments within the code blocks.