
With Visual Studio 17.5 Preview 3.0 , Microsoft has introduced a new Spellchecker. The problem: apparently this is a remotely activatable feature, which is why it was already activated with Visual Studio 17.5 Preview 2.0 from one moment to the next and caused thousands of developers to suddenly receive hundreds of warnings - including me.
Apparently this isn’t a very smart feature for development environments, as common developer identifiers like “ex” for Exceptions were also admonished by the language fix.
With the release of Visual Studio 17.5 Preview 3.0, at least a button has been added to the text editor toolbar to finally disable the feature.
Personally, I always wonder what such a feature has to do in a development environment, especially with features that probably belong more in Word or Outlook. Source code often contains identifiers that are not real words.
Spell checkers in IDEs need to take this into account.
Related articles

Apr 10, 2024 · 2 min read
Welcome to the new Visual Studio SLNX Solution File
For many years, there has been a lot of criticism of Visual Studio’s current solution format. It is very difficult to read, it does …

Oct 29, 2023 · 14 min read
.NET 8 makes you faster. Everyday.
As has been the case for many releases, the .NET 8 team is spending a lot of development effort to improve the .NET Runtime in terms of …

Oct 06, 2023 · 2 min read
Accelerate your .NET build with Visual Studio 2022
A little more than three months ago, Microsoft integrated a new functionality into Visual Studio 2022: Build Acceleration . This mechanism, …
Let's Work Together
Looking for an experienced Platform Architect or Engineer for your next project? Whether it's cloud migration, platform modernization or building new solutions from scratch - I'm here to help you succeed.


Comments