7 Advanced Tips for Mastering Waf DotNetPad

Troubleshooting Common Issues in Waf DotNetPad

Waf DotNetPad is a lightweight .NET editor designed for fast scripting and small projects. This guide covers common problems, diagnostic steps, and fixes so you can get back to coding quickly.

1. Application won’t start

• Symptom: Double‑clicking the exe does nothing or an error dialog appears.
• Cause: Missing .NET runtime or blocked by antivirus.
• Fixes:
  1. Install/repair .NET: Ensure the required .NET runtime is installed (check the product docs for the exact version). Download from Microsoft and run the installer or repair option.
  2. Run from command line: Open PowerShell/CMD in the app folder and run .\DotNetPad.exe to capture console errors.
  3. Check antivirus/quarantine: Temporarily disable or whitelist the exe; restore if quarantined.
  4. Event Viewer: Look under Windows Logs → Application for CLR or .NET runtime errors.

2. Crashes or unhandled exceptions

• Symptom: App crashes during use or throws exceptions.
• Cause: Faulty extension, corrupted settings, or null/reference bugs.
• Fixes:
  1. Start with default settings: Move or rename the settings/config folder (usually in %AppData%\WafDotNetPad or %LocalAppData%) and restart to regenerate defaults.
  2. Disable extensions/plugins: Temporarily remove third‑party extensions to isolate the crash source.
  3. Update app: Install the latest release; many crashes are fixed in updates.
  4. Collect crash logs: Use Windows Error Reporting or the app’s log file to locate stack traces; share them with maintainers.

3. Slow performance or high CPU

• Symptom: Editor is laggy, slow to open files, or CPU stays high.
• Cause: Large files, heavy extensions, or antivirus scanning.
• Fixes:
  1. Exclude folders from antivirus scanning.
  2. Avoid very large files: Split huge files or use a specialized viewer for large datasets.
  3. Disable resource‑heavy features: Turn off live analysis, diagnostics, or preview panes in settings.
  4. Monitor with Task Manager: Identify whether CPU is used by DotNetPad or another process.

4. IntelliSense/auto-complete not working

• Symptom: No suggestions, signature help, or type info.
• Cause: Language service failed, missing references, or corrupted cache.
• Fixes:
  1. Restart language service: Close and reopen DotNetPad or the specific document.
  2. Check project/assembly references: Ensure referenced DLLs are accessible and target the correct framework.
  3. Clear cache/settings: Remove language service cache or reset user settings.
  4. Update tooling: Ensure the editor and any language tooling packages are up to date.

5. File save or permission issues

• Symptom: “Access denied” when saving, or files revert after save.
• Cause: File permissions, read‑only attributes, or cloud sync conflicts.
• Fixes:
  1. Check file attributes: Right‑click → Properties → uncheck Read‑only.
  2. Run as administrator if editing protected system files.
  3. Disable cloud sync temporarily: Pause OneDrive/Dropbox to rule out sync conflicts.
  4. Verify disk space and filesystem health.

6. Theme, font, or UI settings not applying

• Symptom: Changes to appearance don’t persist.
• Cause: Corrupted settings file or multiple config locations.
• Fixes:
  1. Reset UI settings: Rename the UI settings file or reset from Preferences.
  2. Check for multiple installs: Ensure you’re editing the settings for the active installation.
  3. Update the app — bug fixes often resolve persistence issues.

7. Problems running snippets or scripts

• Symptom: Scripts fail to run or exceptions at runtime.
• Cause: Wrong target framework, missing NuGet packages, or runtime restrictions.
• Fixes:
  1. Target the correct framework: Confirm script targets the installed .NET runtime.
  2. Restore packages: Use NuGet restore or add required DLL references.
  3. Check runtime exceptions: Run from command line to view stack traces.

8. Integration with external tools fails

• Symptom: Debugger, build tools, or external compilers don’t work.
• Cause: Misconfigured paths or incompatible tool versions.
• Fixes:
  1. Verify PATH and tool locations in settings.
  2. Use compatible tool versions documented by Waf DotNetPad.
  3. Test external tools separately to isolate the issue.

Quick diagnostic checklist

• Update Waf DotNetPad to the latest version.
• Restart the app and your machine.
• Run from command line to capture errors.
• Temporarily disable extensions and antivirus.
• Reset or move config files in %AppData%/LocalAppData.
• Check Event Viewer and app log files for stack traces.

If problems persist, gather: app version, OS version, logs/stack traces, steps to reproduce, and any active extensions, then report them to the project’s issue tracker or support channel.