Affects Version/s: 1.1
Fix Version/s: 1.2
Number of attachments :
In .Net, it is possible to add a source file as a link (file is visible in Visual Studio but kept at the original location). When the project is analysed in sonar, the source files are not imported but the violations are there. So it's impossible to know where the violation was found.
In the project file (csproj) the source file is referenced like this:
ie: In visual studio I have a folder called CrmCommon that contains the file AbstractFactory.cs, but its location on disk is ..\..\..\CrmCommon\AbstractFactory.cs relative to the project.
We use this functionality to "embed" common code within an Assembly as it is deployed within a database and it needs to be self-contained.
Also it is not possible to exclude the files either (I thought I might at least get rid of the violations if I cannot see where they come from). I tried general patterns like */CrmCommon/.cs without success.