ScintillaNET VS Visual Studio Code

I'm using the ScintillaNET NuGet package. It had its last update 6 years ago. Its last repo commit 5 years ago. The documentation... is lacking - for example, copying example code from there immediately gave me obsolete warnings. Still, this was simply the only library I could find for this.

If you're using Windows Forms, you can also take a look at ScintillaNET (or for WPF inside of a WindowsFormsHost).

It’s actually WinForms 😄. I’m using dockpanelsuite, DarkUI, and ScintillaNET. I forked the dockpanelsuite and DarkUI repos. My modifications to dockpanelsuite adds a docking manager and ability to use extra (non-default) theme files from a vstheme.gz format that the documentation specifies. I then extended DarkUI to accept ThemeBase objects and apply the necessary drawing/coloring styles to the controls.

A code editor (VS Code is my go-to IDE), but feel free to use any code editor you're comfortable with.

First, grab your favorite command-line tool, Terminal or Warp, and a code editor, preferably VS Code and let’s begin.

C# is very good as a language, have developed in it for 5+ years. The problem is the gap between what MSFT promises to management and actually delivers to developers. You really really need to fully read the fine print, think of the omissions in documentation and implement a proof-of-concept that almost implements the full solution to find out the hidden gotchas.

For example, even probably their best product VS Code only got reasonable multiple screens support last year: https://github.com/microsoft/vscode/issues/10121#issuecommen...

And then, on the other end of the spectrum, you have Teams.

Hey fellow amazing developers, we got you Essential VS Code Extensions for 2024 (these are especially important for web developers) recommended by our developers at evotik, we wont talk about ESlint nor Prettier which all of you already know.

Visual Studio Code (VS Code): Developed by Microsoft, VS Code is a lightweight yet powerful IDE with extensive support for Python development through extensions. It offers features like IntelliSense, debugging, and built-in Git integration.

In VSCode for example this can be easily done by adding the following .vscode/launch.json file:

I had a near-identical experience. I looked into switching in 2019 and ran into this 2016 bug which was a showstopper for me. Fixed it myself, grand total 4 line diff. https://github.com/microsoft/vscode/issues/10643

When working in Visual Studio Code (VS Code), always create a new Python file for your project.

Code Editor: Choose a code editor like Visual Studio Code that offers good support for web technologies and extensions for PWA development.

When working in Visual Studio Code (VS Code), create a new Python file for our music player project. It's helpful to have separate files for different parts of your project.