Skip to main content

C# Plugin Guide

Best for mature desktop integrations

The C# SDK is the stronger choice when the plugin belongs in a .NET world or when you want the most mature-looking public Logitech plugin workflow.

1. Official setup​

The public docs currently describe this flow:

dotnet tool install --global LogiPluginTool
logiplugintool generate Example
cd ExamplePlugin
dotnet build

The build should create a .link file for the Logi Plugin Service.

2. Development loop​

cd ExamplePlugin/src
dotnet watch build

The SDK docs describe this as the hot-reload workflow for plugin development.

3. What C# is good for​

Choose C# when:

  • your app already has .NET domain logic,
  • you need robust desktop architecture,
  • you want strong typing for large plugins,
  • you want to reuse internal libraries,
  • you prefer Visual Studio or Rider workflows.

4. Packaging​

The official tooling packages plugins as .lplug4.

That package can be:

  • verified,
  • installed into Logi Options+,
  • submitted to the Marketplace.

5. Example packaging commands​

logiplugintool pack ./bin/Release/ ./MyPlugin.lplug4
logiplugintool verify ./MyPlugin.lplug4

6. When C# is the better choice than Node.js​

Use C# when:

  • plugin complexity is growing,
  • your integration includes long-lived services or richer state,
  • Windows desktop behavior matters,
  • the team is not primarily JavaScript-based.