Skip to main content

NDepend–Don’t extract it in your Program Files!

A few weeks ago I was contacted by Patrick Smacchia, the creator of NDepend, if I would check out the latest edition of their code quality tool. As I had an upcoming software audit assignment planned, I thought it would be a great occasion to see what NDepend brings to the table and how it can help me to improve my understanding of an unfamiliar codebase.

After a reply to Patrick I got a link to the Professional edition but you can download a trial version here. NDepend doesn’t have an installer but is provided as a zip file.

I extracted it to my %Program Files% folder and had a look at what was in there:

VisualNDepend.exe looked promising so I double clicked on that executable. Unfortunately nothing happened !?

Hmmm, maybe I should not be so eager and first read the README.txt file available in the zip?

OK, the first 2 lines in the README immediatelly point out my mistake;

This file contains information about NDepend files when unzipped.
Don't unzip these files in '%ProgramFiles%\NDepend'.
This might provoke problems because of Windows protection.

And indeed after extracting it to another folder, I could run the executable. Time to start our journey! (But that is for another post)

Remark:

In case you really want to install NDepend in your %Program Files%, you should right click on the zip file before extracting and click on Properties.

In the Security section at the bottom, check the ‘Unblock’ checkbox and choose ‘Apply’. If you now extract it to your %Program Files% it should work.

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more