Skip to content

Use Glutinum to generate bindings for VS Code #56

@NatElkins

Description

@NatElkins

Session on Use Glutinum to generate bindings for VS Code

Nat Elkins, from NELKNET in Eastern (NYC) would like to tackle:
glutinum-org/cli#152
glutinum-org/cli#153
glutinum-org/cli#154

Extra

I am trying to bring .NET debugging to VS Code fork IDEs like Cursor and Windsurfer (among others). The Microsoft .NET debugger is licensed to only work in VS Code though. There is an alternative debugger, https://github.com/Samsung/netcoredbg which I got working in Cursor. But it's kind of a pain to use since you need to build it on your machine, or set up a custom kind of launch.json config, etc. I want to have an extension I can just install that will install and use the correct debugging package. And I want to write that extension in F# using Fable. I know there are some existing helpers for VS Code here (https://github.com/ionide/ionide-vscode-helpers) but they're somewhat outdated and Glutinum is allegedly the more up-to-date way of generating bindings. That's what led me down the route of trying to get Glutinum to generate VS Code bindings.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions