Is there anyway to avoid having CustomDictionary.xml uninstalled when FxCop is uninstalled before installing a new version? It would be nice to be able to keep the work I put into collecting various words/acronyms not found in the Office dictionary.
Thanks
We've discussed this in the past. Right now, we're re-examining the spelling services and I will put this point on the list for consideration.
In the meantime, you might want to place the customdictionary.xml in your user settings directory. FxCop will pick it up, and it won't be blasted on an uninstall. After installing a new version, you can copy over the file and hope we haven't altered the format. 8)
C:\Documents and Settings\mikefan\Application Data\Microsoft FxCop\1.35\CustomDictionary.xml
Michael Fanning - MS wrote:
In the meantime, you might want to place the customdictionary.xml in your user settings directory. C:\Documents and Settings\mikefan\Application Data\Microsoft FxCop\1.35\CustomDictionary.xml
Thanks, I'll do that.
There seems to be a push towards developing in a partial trust environment (e.g. Visual Studio no longer needs full trust to run--haven't tried it). In that situation the user may only have write access to the user settings located file. Has any thought been put into installing and accessing user-specific data into the user settings directory to be partial trust friendly?
Peter,
Users with low rights by default have both write and read access to the folder under their own user profile, so it shouldn't be a problem.
By-the-way, the folder Mike pointed to should actually be:
C:\Documents and Settings\mikefan\Application Data\Microsoft FxCop\1.32\CustomDictionary.xml
As the settings file format hasn't changed, we haven't bumped up the version on that, and we will continue to use settings set in 1.32.
Regards
David
Sorry, I was referring to User-specific files such as "c:\Program Files\Microsoft FxCop 1.35\CustomDictionary.xml" and low rights.
Users with low rights by default have both write and read access to the folder under their own user profile, so it shouldn't be a problem.
Not to mention shared machines where one user would like certain words where the other does not. The default setup does not "allow" that (yes, we can do what Michael has suggested; but that will get circumvented on the install of the next release).
We don't actually encourage users to modify C:\Program Files\Microsoft FxCop 1.35\CustomDictionary.xml, because, as you've noticed it gets blown away when you uninstall.
Mosts users (both internally and externally) actually scope the custom dictionary per FxCop project (simply put it in the same folder as the project), as there are typically certain words that should only be recognized in certain projects but not others.
Ahh, I must have misread the docs then. Being able to have an custom dictionary per project is outstandingly useful.
Thanks
