![create custom dictionary in word 2013 create custom dictionary in word 2013](https://erinwrightwriting.com/wp-content/uploads/2019/07/Word-2019-Custom-Dictionaries-Dialog-Box-Dictionary-List_v2.jpg)
Setting the build action property of the xml file to CodeAnalysisDictionary, makes VS include the switch /dictionary:" " to the FxCop command. If you examine the build output window, Visual Studio makes a call to FxCop.exe with a whole load of parameters. Recompile your project and FxCop should no longer complain about those words. In the properties for the XML file you've created (right-click, properties), change the Build Action to ' CodeAnalysisDictionary'.
![create custom dictionary in word 2013 create custom dictionary in word 2013](https://cdn.extendoffice.com/images/stories/doc-outlook/add-dictionary/doc-dictionary-2.png)
You can then edit this file to include your own words.
#CREATE CUSTOM DICTIONARY IN WORD 2013 INSTALL#
As a starting point, copy the XML from the CustomDictionary.xml that comes with FxCop which is in the default FxCop install directory which on my machine is C:\Program Files\Microsoft Visual Studio 9.0\Team Tools\Static Analysis Tools\FxCop\CustomDictionary.xml. xsd schema file available (that I can find). The dictionary file must follow the correct schema, but unfortunately, there does not appear to be an. It doesn't need to be called CustomDictionary.xml. Here's how.Īdd a new XML file to your project or solution and call it what you want. In Visual Studio 2008, you can add a dictionary xml file to the solution and then tell the solution to use this as the dictionary for FxCop. There seems to be a few posts out there asking where to put a custom dictionary to be used by FxCop (code analysis).