High On .NET
Productivity tools for .NET developers using Visual Studio Code.
High On .NET is a growing collection of small tools that remove everyday friction from .NET development.
Usage
- Open an
.fsx file
- Add a breakpoint
- Run:
HighOn.NET: Debug Current FSX Script
- Start debugging
That's it.
Requirements
- Visual Studio Code
- .NET SDK installed
- use vscode extension:
ms-dotnettools.vscode-dotnet-runtime
- run command:
csdevkit.installDotnetSdk
- Windows (Linux 🚧 Planned)
- * nice to have vscode extensions:
ms-dotnettools.csdevkitIonide.Ionide-fsharp
Why?
.NET development often requires repeating the same small tasks:
finding SDKs, creating configurations, running commands, and switching between tools.
High On .NET turns these workflows into simple commands inside VS Code.
Features
| Feature |
Status |
Debug F# scripts (.fsx) directly from VS Code |
✅ Available |
Automatically find the correct F# Interactive (fsi.dll) |
✅ Available |
No launch.json required for FSX debugging |
✅ Available |
| More .NET developer productivity tools |
🚧 Coming soon |
Debug F# scripts
Debugging an .fsx file should be simple.
Normally you need to create a custom launch.json:
{
"type": "coreclr",
"request": "launch",
"program": "C:\\Program Files\\dotnet\\sdk\\9.x.x\\FSharp\\fsi.dll",
"args": [
"${file}",
"--debug+",
"--debug:portable",
"--optimize-"
]
}
The problem:
- SDK versions are different between machines
fsi.dll path changes after SDK updates- every developer needs their own configuration
High On .NET removes this setup.
Roadmap
High On .NET will grow into a collection of .NET productivity tools.
Ideas:
| Tool |
Status |
| F#: script debugging |
✅ Done |
| Build/Restore nearest fsproj or csproj by context |
🚧 Planned |
| Starter framework templates |
🚧 Planned |
| Snippets |
🚧 Planned |
| More ideas |
💡 Open |
Contributing
Found a repetitive .NET workflow that could be automated?
Open an issue and share the idea.
License
MIT
