This release contains a significant change in the way the spell checker configuration options are handled. There is one global configuration as before. However, spell checker configurations can now be created within solutions at the solution, project, folder, and file level. This allows you to define different settings at each level while inheriting the options that are not changed from higher level configurations. A new configuration editor window is used to modify the global configuration settings and all configuration settings files within a solution.
Other changes in this release:
Fixed up an issue in the CommentTextTagger that was causing it to not spell check XAML elements and some XML elements.
Fixed SquiggleTaggerProvider so that it does not create unnecessary duplicate instances on views when called multiple times.
Added the back tick (`) and ellipsis (…) characters as valid word break characters.
Moved some configuration settings to different pages to better group the options.
Split the Excluded Extensions option out on to its own page and made it a list-based property.
Added support for specifying additional dictionary folders. These will be searched for dictionaries to make available as a selectable language for spell checking and can be solution, project, folder, or file-specific.
Added a configuration option to specify whether or not to determine the dictionary language for localized resource files based on their filename. For example, if the file LocalizedForm.de-DE.resx is opened in the XML file editor, the German language dictionary will be selected and used automatically if available regardless of the default language that is specified in the configuration settings.