Sonar .NET Ecosystem

Be able to specify additional path for FXCop assembly resolving

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 0.3
  • Fix Version/s: 0.4
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    1

Description

My fxcop analysis fail because it doesn't found additional assemblies, which are stored in a "Lib" folder (relative path).
Sometimes it's because some assemblies depends on version 1.X but I'm using "assembly binding" to force version 2.X. But in this case, FXCop need the 1.X version to run the analysis.

I'm able to fix it manually with the current settings in FXCop:
<Targets>
<AssemblyReferenceDirectories>
<Directory>$(ProjectDir)/Lib/Spring.net/1.3</Directory>
<Directory>$(ProjectDir)/Lib/NHibernate/2.0</Directory>
</AssemblyReferenceDirectories>

As a dotnet-maven user
I want to set additional path in the POM.xml
To be able to run fxcop analysis in my project

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Mathias kluba added a comment -

[INFO] Initializing Introspection engine...
[INFO] Could not resolve reference to NHibernate.
[INFO] Analysis Complete.
[INFO]
[INFO] NOTE: One or more referenced assemblies could not be found. Use the '/directory' switch to specify additional assembly reference search paths.

Show
Mathias kluba added a comment - [INFO] Initializing Introspection engine... [INFO] Could not resolve reference to NHibernate. [INFO] Analysis Complete. [INFO] [INFO] NOTE: One or more referenced assemblies could not be found. Use the '/directory' switch to specify additional assembly reference search paths.
Hide
Permalink
Alexandre Victoor added a comment -

Is it an issue specific to FxCop or do you have the same kind of issue with Gendarme ?

Show
Alexandre Victoor added a comment - Is it an issue specific to FxCop or do you have the same kind of issue with Gendarme ?
Hide
Permalink
Mathias kluba added a comment -

I submitted a patch, but there's no Unit tests for the Mojo...
It's only a FXCop Issue: the problem occurs also with the GUI, but it prompts "where is the DLL?" and you have to enter a path, so it adds it in the <AssemblyReferenceDirectories> (same thing as the /d parameter)

I really don't know why FXCop need to get the referenced assemblies to scan mines...

Show
Mathias kluba added a comment - I submitted a patch, but there's no Unit tests for the Mojo... It's only a FXCop Issue: the problem occurs also with the GUI, but it prompts "where is the DLL?" and you have to enter a path, so it adds it in the <AssemblyReferenceDirectories> (same thing as the /d parameter) I really don't know why FXCop need to get the referenced assemblies to scan mines...
Hide
Permalink
Alexandre Victoor added a comment -

Mathias,
Do you have the same problem when running gendarme ?
Please could you provide a minimalist VS solution that illustrates this issue ?
Regards

Show
Alexandre Victoor added a comment - Mathias, Do you have the same problem when running gendarme ? Please could you provide a minimalist VS solution that illustrates this issue ? Regards
Hide
Permalink
Alexandre Victoor added a comment -

patch applied

Show
Alexandre Victoor added a comment - patch applied
Hide
Permalink
Alexandre Victoor added a comment -

released in version 0.4

Show
Alexandre Victoor added a comment - released in version 0.4

People

  • Assignee:
    Alexandre Victoor
    Reporter:
    Mathias kluba
Vote (1)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: