I’ve been managing a cluster of programming related links I use regularly for a while. Although it can quickly become a dumping ground instead of organized; figured this would be a good place to actually organize major references I use. Notice that the right side of this page is a category TOC.

.Net Framework

  • Source Code

    • .Net <= 4.8 Source Reference, this is a labyrinth, but completely invaluable if you are trying to figure out what all you will lose when overriding the metadata of a dependency property.
    • .Net Core Source Reference, invaluable for the same reasons, but probably more so since Core has been going through so many changes.
  • WPF

    • FrameworkElement Class, this is the base element for all the elements you might be referencing, I use this page to explore Control inheritance.
  • UWP

    • Win2D Documentation, this gives .Net drawing capabilities similar to the Canvas control with JavaScript.
    • FrameworkElement Class, this is the base element for all the elements you might be referencing, I use this page to explore Control inheritance.
  • XAML

    • XamlFormatter VS Extension, this thing is a great time saver. I like the fact that it takes absolutely no liberties with line spreading, but I do wish it had a “format selection” version that did auto-stack horizontal properties for me.
    • Developing Windows 10 Applications with C# by Sergii Baidachnyi, this is a crap title for this book. Its largely focused on XAML and probably the only one I’ve found that is. Yes, there are WPF as a platform books, but this is fairly laser focused and honestly a great read. Other than the deceptive title, its a high quality book on the topic of UWP XAML; which is conceptually no different than WPF XAMl.



  • Base64 Encode/Decode Visual Studio Extension. Strictly for text, but this has been saving me quite a bit of time because I can stay directly in VS if I need to serialize a XAML resource or something.

  •, I pretty much use this exclusively when I need to serialize an image for static browser representation; which happens more often than I would like.


  • Angular Palette Generator, priceless tool for outputting exactly the format needed, pick a color, copy and paste.
  • Angular Color Tool, this is a fantastically simple tool that provides colors that go together.
  • Paletton, this is a fantastic online app for application color palette selection. I am red-green color blind, so this helps me out quite a lot.
  • Flat UI Color Picker, another fantastic resource that groups colors that go together with a variety of output color formats.
  • W3 CSS Color Specification, literally everything you need to know about web colors.
  • W3 Schools Web Color Palette, I like to use this for base color selection, just because it has fairly large color swatches and still manages to get quite a few on the screen at one time.
  • System.Windows.SystemColors, definitions of the .Net static resources.
  • System.Windows.SystemColors, subjective, but a good visual reference for .Net static resources.


  • Segoe MDL2 Assets, I frequently use this native Windows 10 font with windows apps to create vector Icons. This page shows the available symbols.
  • Getting Started with Google Fonts, This has definitively been one of the major changes beautifying the internet for us.

HTML Canvas



  • Editing

    • Typora, I know MD-Monster is the gold standard, but this is a really nice free MD editor. Offers a “unique” experience in that you work in the “pretty view” of a rendered MD file, but it will dynamically show a lot of the stuff you might care about in the “ugliness” of markdown as it becomes contextually relevant to the cursor location. I use it for almost all my MD editing. Note it does have quick way to switch the view to “raw source” mode too.
    • Markdown All In One, this is a VSCode extension that can do quite a lot of stuff, but doesn’t give you that “hybrid” view Typora will. I currently use this for dynamically generating the TOC’s.
  • Syntax

  • Viewers

    • Quicklook, this is a general enhancement for windows that opens a “view” of many different types of documents from Windows File Explorer just by pressing the spacebar. I am especially fond of the automatically generated table of contents this makes markdown files.
    • Markdown Preview Enhanced, if you didn’t like Typora and the raw Markdown is your cup of tea, then this is probably the best VSCode Extension viewer to use in conjunction with Markdown All In One.


  • HTML5 Patterns, a great source for commonly used Regex Patterns.
  • RegExr, my go to source for building and debugging Regex patterns.
  • ExtendsClass Regex Tester, this is easily the best Regex logic visualizer I’ve seen and it has more defined language types. I would choose this over RegExr for complex pattern building.
  • MS Regex Quick Reference, because you need to verify the feature you used in the builders actually exist when used in .Net applications.


  •, excellent place to find app sound effects.
  • Sonic Pi, if you like coding and electronic music, then this is probably the coolest thing ever.

Visual Studio Code

  • API

    • NodeJS API Documentation, because VSCode is built on and thus exposes NodeJS functionality.
    • VSCode Language Server Protocol Specification, this is for deep dive research.
    • VSCode API Documentation, this is for investigating everything in the vscode namespace.
    • VSCode Predefined Variable Reference, these are all the ${special} keywords that do stuff in the JSON.
    • VSCode Debugger Extensions, this is a fantastic overview of the debugger API and there is a link to a GitHub repo showing you how to simulate a Mock Debugger made entirely from TypeScript; which is the only way you’ll be able to test code if the thing your targeting doesn’t expose a debug adapter.
    • Haxe, for some reason the Haxe language required its own implementations of VSCode. This is a derived work, but they also wrote a lot of their own documentation. With that said, you can sometimes find different explanations for things here that might make something about the real VSCode API more understandable.
  • Reference Repos

This post is licensed under CC BY 4.0 by the author.