The article covers essential steps on how to create a typical extension for the Visual Studio Code and publish it in the marketplace. It also explains how to automate the publishing of releases on GitHub instead of manual calls of the CLI. Useful links for a quick start are provided.
In the previous article StyleCop with team-shared rules and auto-update I've covered how to package StyleCop analyzers as a Nuget package, and distribute it to the team with automatic updates. While that approach is still valid, the part related to the Nuget project itself is overcomplicated and cumbersome. This time I'd like to show a simpler and easier way how to package any Roslyn analyzers including StyleCop and all related settings.
How to deserialize a part of JSON as a string keeping everything inside as is including the formatting? Or how to merge JSONs together into one having them provided as strings? The article shows an implement of a custom converter for the
System.Text.Json that does described things, and provides additional cases when such converter might be useful.
The post covers how to implement StyleCop analyzers with automatically updating team-shared rules and settings. The described approach works both in Visual Studio and Rider and on any CI.
Exactly 1 year ago we arrived in Munich. New country, new city, new job, new life.
This post is about living here: a personal opinion what was wondering and unusual comparing to the Ukraine, what is really good and what annoys every day.
A quick question to check the knowledge how
enum values work under the hood.
Recently I've developed a simple processing application that generates some data in the database. For business logic it was important to understand what entity was created the last on some steps. Since there was no concern about scaling or running several instances simultaneously, it was decided to use the primary key itself, the auto-incremental integer value. I didn't want to rely somehow on date-time or invent something sophisticated.