One of the dependencies in my application is on:
Microsoft.Office.Interop.Outlook
when fxCop can't find it and prompts me to browse for it it, the file dialog box prompts me to look for Office.exe or Office.dll and won't let me change it to the correct name in order to find this dependency.
Is this a bug It's not a big issue - I've been able to ignore it, but it would be nice if there were a fix because I get it everytime I run fxCop.
Thanks,
Chuck
A Minor fxCop Bug??
Avitus
Hi David...
The problem I have is that the File Dialog box you've implemented does not allow me to override the default selection by entering "*.*".
Thanks,
Chuck
Alan2007
Hi David,
I am using version 1.3.5. The unfortunate thing is that it locks you into selecting the dependency it thinks is right and doesn't allow you to select a variation (like Microsoft.Office.Interop.Outlook.dll instead of Outlook.dll.
Thanks
Chuck
Idrise
Chuck,
I can't repro this. I just tested this and FxCop asked me for either Microsoft.Office.Interop.Outlook.dll or Microsoft.Office.Interop.Outlook.exe.
What version of FxCop are you running
Regards
David
bramble
Chuck,
Are you sure I'm not talking about the Files types combo, but rather the actual file name combo. Can you post the exact steps you are using
Bibi Watson
Chuck,
Although in my tests it asked for the correct dependancy (in this case Microsoft.Office.Interop.Outlook.dll), like all common dialogs, you can get Windows to show all files by entering *.* in the filename combobox, this allows you to select an assembly with a different name.
Hope that helps
David