Whereas I’m restricted to composing comments in code, even I recognize the esteem of comments placed on a class or method declaration (I’m barring properties since most don’t require commenting). Apparently, if you’re composing these comments it’s with the trust that somebody will, someday, read them … and it would be dreadfully humiliating in case you incorrectly spelled things in those comments.
If that sounds like a issue worth tending to, go to Visual Studio’s Tools menu and select the Extensions and Update menu choice. Within the resulting dialog, select Online from the tabs on the left and enter “Spell Check” (with the space in the center) in the search box.
You’ll get a list of spell checkers that you simply can add to your applications but, in Visual Studio 2017, you’ll moreover get Eric Woodruff’s Visual Studio Spell Checker. It’s an extension of an earlier spell checker for Visual Studio (which prior adaptation is still accessible through GitHub in case you don’t discover it in Extensions and Updates).
After downloading the extension, you’ll need to closed down Visual Studio and hold up calmly for Visual Studio’s installer to appear. Clicking the Alter button within the installer window will install Spell Checker. Once you restart Visual Studio, you’ll discover a new Spell Checker choice on Visual Studio’s Tools menu with a sub-menu containing parts of alternatives.
If you choose the choice to spell check your entirety solution, then you’ll find that Spell Checker checks all comments and all strings — likely finding more blunders than you care to do anything almost (for case, I wouldn’t consider “App.config” in a comment to be an mistake). Luckily, you’ll prepare Spell Checker to ignore words (like, for example, “App.config”) or configure what Spell Checker checks (through Tools > Spell Checker > Edit Global Configuration).
You’ll be able discover it more about Spell Checker here. It would be a disgrace in case a few afterward programmer thoughtless of you because you spelled something off-base.