Put Your Visual Studio Extensions Back Into the Main Menu
Visual Studio 2019 has an annoying behaviour when it comes to extensions. By default, they are not directly accessible in the menu bar, they are hidden in the Extensions menu:

Visual Studio 2019 has an annoying behaviour when it comes to extensions. By default, they are not directly accessible in the menu bar, they are hidden in the Extensions menu:

The SQL Server Management Studio (SSMS) has a simple way to increase the font size of your query. (You can select a value between 20% and 400% in the bottom of that window). But when you try to increase the font size in the result grid, you find nothing. We always have to guess what it says when we share our screens in a Teams meeting. Luckily, someone in my team found the way to fix that problem.
We use StyleCopAnalyzers (the successor of the StyleCop package) to get consistent code in all our projects. While it is sometimes annoying, it is the simplest way we found to enforce code style guidelines. Since we use it in all our projects, we want to reuse our customised ruleset.
In the good old days doing web development was a lot simpler. We just open a HTML file from the local filesystem in our browser and the referenced CSS and JavaScript files where loaded as well. We could focus on getting our web site right without the need for a local server or any other infrastructure.
Naming is important and when you find a more precise one, you not only should update your code but your database as well. SQL Server has the function sp_rename to rename objects in your database.
We all wanted to be in Norway for NDC Oslo 2020, but Covid-19 made that impossible. As with most other conferences in 2020, there was no way to make this an in-person event. The NDC crew and Dylan Beattie did their best to create the typical NDC feeling at an online-only conference. I was surprised how well it worked and how few problems occurred for an event with around 1000 attendees.
Visual regression testing is the last part I write about the NDC Oslo 2020 workshop Front End Web Fundamentals hosted by Amy Kapernick (@amys_kapers). This kind of testing is a nice extension to my testing toolbox and can help you to get an alarm when you unintentionally change your user interface.
When you work with Pa11y you may get errors as I described in an earlier blog post:
Last month I attended the NDC Oslo 2020 online workshop Front End Web Fundamentals hosted by Amy Kapernick (@amys_kapers). In my first post on this workshop I wrote about the tools we used and resources that can help you to create better web applications.
Today I focus on accessibility. I am not an accessibility expert, yet the most errors you make are easy to find and do not need much time to fix. It will not replace an accessibility expert when you are required by law to follow certain levels, but it will make their work a lot simpler if the most common mistakes are already fixed.
The main reason to I wrote this post is to remember the different steps I had to take. Your challenges may be different, but if you follow the same structure, you should be able to tackle them as well.
So far, I used separate statements to add a new column to a table, set a default value and add a foreign key relation to another table. However, we can do these 3 steps in one single command: