Skip to content

Troubleshooting

Jump to bottom
Tareq Imbasher edited this page May 9, 2024 · 9 revisions

These are common issues that some users will run into and how to resolve them.

NetPad cannot find my .NET SDK installation

NetPad will search the following locations by default (in order):

Windows:

  • {HomeDirectory}\.dotnet
  • C:\Program Files\dotnet\x64
  • C:\Program Files\dotnet

Linux/macOS:

  • {HomeDirectory}/.dotnet
  • /usr/local/share/dotnet
  • /usr/share/dotnet
  • /usr/lib/dotnet
  • /usr/lib64/dotnet
  • /opt/dotnet

If it cannot find your .NET SDK installation in any of those locations it will attempt to execute dotnet from your $PATH and use it if it's found.

You can tell NetPad where your SDK is installed by going to Settings > General > Folders and adding the full path to your .NET SDK installation directory in the .NET SDK setting.

NetPad is damaged and can't be opened

image

If you get this message on macOS this means your system is configured to not allow unsigned apps to run. NetPad is not yet a signed application and on most macOS systems users are likely to receive this message.

To resolve this issue, open a terminal and execute:

xattr -cr /path/to/NetPad.app

NetPad will run normally afterwards. See this discussion for a tip.

NetPad does not start on Windows [Error: listen EACCES: permission denied]

image

If you get this message when starting NetPad on Windows, try these possible solutions:

  1. Disable then re-enable one or more of your network interfaces. See issues #159 and #111.
  2. Restart winnat. See this SO answer for details.
Clone this wiki locally