The bloated IDE from Microsoft, that used to be even more bloated and a lot more expensive. Nowadays it’s a bit sleeker, and a lot more affordable – and it’s the number 1 choice for all the slightly more hardcore development I do.
I do use Visual Studio code (VSCode) for lighter tasks, though!
This tag applies to pretty much all the generic Visual Studio -stuff, if there’s something version-specific, I’ll be using more specific tags, too.
This article explains a couple of easy fixes for an issue, where Visual Studio refuses to properly recognize the FluentUI components you might have used in your Blazor projects. Because apparently that can (kind of randomly) happen! Problem The screenshot below shows a sample from Microsoft’s basic Teams tab extension…Continue reading Intellisense not working for Fluent components in Blazor project? Easy fix!
This article explains a couple of workarounds to a frustrating issue I had with vite and yet-another-weird-frontend-build-toolkit. Because every toolchain for frontend stuff is different, apparently. And they all fail in different ways. Anyway – let’s get to it. Background I was just creating a tiny bugfix to an older…Continue reading External path “**” cannot have more than one “*” wildcard with vite?
This quick blog post explains a couple of very simple fixes – essentially, user errors – to a simple problem that you might run into with Visual Studio when developing the latest of your cool Azure bits. Well, to be fair, a few simple fixes and one heavyweight. A final…Continue reading The simplest fixes to “500 (Internal Server Error)” from Azurite