Software development on Windows can be a pain. Not because of any issues with C#, .NET or the operating system, but simply because the tools surrounding your work can be quite clunky by default. I'm talking about the lack of a package manager, PowerShell's ugly blue terminal with no tabs and a bunch of "missing" tools (git, ssh). It's like a living room where all the furniture is perfectly positioned to stub your toe.
That said, you can get have a pretty nice developer experience if you install a few tools. This post goes over my preferred setup on a new Windows laptop. It's not a definitive guide, just some tips and tricks that I've picked up from other devs that I've worked with. Hopefully you find some of them useful.
The post below summarises everything in this video.
ConEmu my #1 favourite tool for Windows. It allows you to:
It's like removing a rock from your shoe: an ugly blue rock. Some people also like to use Cmder for the same use-case.
Windows Explorer search is so horribly broken in 2020 that you hope Microsoft is trolling you, because the alternative is just sad. In any case Everything gives you very fast search of all your files and folders, including that pesky InternalToolChain.dll which has gone missing.
I believe it runs in the background all the time, quietly indexing your files. I do not how this affects your workstation's performance.
Chocolatey is the (unofficial) package manager for Windows.
NuGet is good for installing your .NET libraries, while
choco is good for everything else.
It's great for quickly installing tools and automating the process. It's quite easy to install.
To install a tool like Everything, you can just search for it then run the install from the CLI:
choco install everything
In fact, once you've got choco installed, you can install all of the other tools on this list with:
choco install git -y choco install conemu -y choco install everything -y choco install poshgit -y choco install vscode -y choco install ag -y
Try not to install anything with Chocolatey if it already exists: things can get weird. You can always run
Get-Command in PowerShell to check for existing executables:
Visual Studio Code is a text editor that strikes a great balance between being full-featured and overly bloated.
This is an obvious proposition to more experienced developers, but there are a lot of beginners out there editing their files in
I personally prefer it to slimmer alternatives like Sublime Text 3 and hulking behemoths like PyCharm or Visual Studio.
A really cool feature of VSCode on Windows is that it's quite command-line friendly. You can open the current folder in VSCode from the CLI with:
or you can open a single file like this:
Sublime Text 3 is a popular alternative with a rich plugin ecosystem but less features out-of-the box. Some people also like Notepad++, a decision I don't really understand, but as the name suggests, it beats the shit out of just using Notepad.
There's a few tricks to getting PowerShell into a usable state on a new Windows machine. The first thing is to always open as Administrator, if you can. Once PowerShell is open, I like set the "execution policy", which allows you to run scripts:
Set-ExecutionPolicy -ExecutionPolicy Bypass
Now you can put some PowerShell in a script, like myscript.ps1:
# myscript.ps1 Write-Host "Hello World!"
and then run it from your PowerShell terminal
./myscript.ps1 # Hello World!
Finally, I like to configure my profile, which is a script that runs before every PowerShell session starts.
This is where you can add things like welcome messages, function definitions and module imports.
To set up your profile, just open
$profile, add some stuff and then save the file. For example:
One other handy PowerShell tip while I'm here: you can open folders in explorer with
explorer, and, if you're not using VSCode,
you can still edit files using
explorer . explorer "C:\Users\mattd" notepad "secret-plot.txt"
This one also seems kind of obvious if you're already using Git,
and if you're not using Git then why would you bother?
Wait! There's more than just
git in Git for Windows. The install also gives you:
sshfor logging into Linux servers
scp for transfering files to Linux servers
ssh-keygen for generating SSH keys
A bunch of nice Unix tools like
You'll never need ot use PuTTY again! You might scoff at my promotion of Git Bash:
Fool! Doesn't he know about Windows Subsystem for Linux?
WSL seems nice, but a lot of workplaces won't let you install it, but they will allow Git.
Posh-Git gives you a nice little Git status message in your command prompt. It tells you the current branch that you're on and the number un-comitted changes. It's quite convenient. To install it:
Install-Module posh-git -Scope CurrentUser -Force
And then to activate it:
Note that it will only display your Git status when the current directory is a Git repo. Consider placing the import statement into your PowerShell profile so that it loads automatically for you.
The Silver Searcher is a nice little CLI tool for quickly finding all instances of a string in a folder. For example if I want to find all instances of "probably" in my "contents" folder:
ag -i probably content
Its main appeal is speed: it's really fucking fast. Git grep is also a contender if you're working in a Git repository:
git grep probably
Despite Steve Ballmer's pro-dev yelling in the 2000s, Microsoft dropped the ball on making Windows nice for developers. Nevertheless you can use these tools, and others, to cobble together an environment where building software isn't like stubbing your toe on every piece of furniture. If you haven't tried these tools already, then I encourage you to install them and have a play around. You might find your coding experience a little less painful.
If you have any feedback or questions email me at [email protected]