NDepend Users Voice

Add support for .NET Core packaged application analysis

When .NET Core assemblies and applications are built and packaged using dotnet CLI (e.g., "dotnet pack") the build output isn't a folder full of assemblies the way it was in classic .NET - it's a NuGet .nupkg file with the assembly (or full application) inside.

In the case of applications, this includes not only the entry point (e.g., "MyApplication.exe") but also any dependent assemblies required to make the app run. That even means all of the base framework assemblies ("System.Collections.dlll") - there is no reference to any installed .NET Framework. The dotnet CLI and runtime take care of that and the whole application is packaged. "Pay for play," as it were.

The idea for analyzing NuGet packages (https://ndepend.uservoice.com/forums/226344-ndepend-user-voice/suggestions/8619250-ability-to-analyze-nuget-packages) is somewhat related to this. If you add support for NuGet packages, this probably wouldn't be too much more of a step.

The idea for analyzing VS solutions (https://ndepend.uservoice.com/forums/226344-ndepend-user-voice/suggestions/4558407-reference-vs-solutions-from-the-ndepend-project) may be helpful for folks using Visual Studio, but you don't need that with .NET Core and the dotnet CLI - with those you may be looking at tooling more like Visual Studio Code, so it'll be interesting to natively support the analysis of packaged applications rather than assuming it'll work somehow through Visual Studio.

7 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Travis IlligTravis Illig shared this idea  ·   ·  Admin →

    0 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base