Skip to content

Troubleshooting

Jump to bottom
Tareq Imbasher edited this page Aug 17, 2023 · 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:

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

Linux/macOS:

  • /usr/local/share/dotnet
  • /usr/share/dotnet
  • /usr/lib/dotnet
  • /opt/dotnet
  • {HomeDirectory}/.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. Otherwise it will show you a message that it cannot find the installation path.

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. You should move it to the Trash.

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.

Clone this wiki locally