It appears that, if there are say 8 issues all-together within the project you've analyzed, but after filtering there is only one, you get the same issue listed 8 times, as the attached screenshot shows.
Code Analysis - The Code Issues window shows duplicate entries for linked files
Answers approved by DevExpress Support
We have fixed the issue described in this ticket and will include the fix in our next maintenance update. To apply this solution before the official update, request a hotfix by clicking the corresponding link for product versions you require.
Note: Hotfixes may be unavailable for beta versions and updates that are about to be released.
- v17.2.3Download Official Update
- v17.1.10Sign in to Request Hotfix
Hi Mark,
I tried to reproduce the issue in a simple sample but failed. I created a solution with multiple projects and every project contains one or more code issues. All issues were shown correctly with our without filtering. Here is a screencast showing my attempts:
https://www.screencast.com/t/tE7HyvYSAgF
Can you please send us a sample project and screencast to show your actions so we can try to reproduce the issue?
Alex, in my case this was done at a solution level. Let me see if I can work out the steps to reproduce, and then if able to see if I can reproduce it with a sample project
Turns out, this may not be anything to do with the filtering, but more over the fact that it's reporting mis-spelling multiple times. I will see if I can provide a sample to illustrate this.
Alex, the reason issues are being reported multiple times, is when there are linked files in play. In the example I've attached, I have linked Class1 from the Test Project to One2One.WCF project. Within this class there is a mispell of the word timezone, you will notice in the attached screenshot (contained within the zip folder) that this has been reported twice.
May need to add a post process to filter out duplicate entries to prevent this scenario. I hope this better illustrates what I discovered during my recent usage of CodeRush with Roslyn.
Mark,
Thank you for your research and providing the sample to reproduce. I can see the issue and we are working on it.
Not a problem, glad I was able to clarify what caused this behaviour to occur.