Project Structure

Project Structure

A clear structure helps keep SDK-based plugins maintainable. Separate startup, features, UI, and licensing concerns early.

Suggested structure

MyPlugin/
├─ Features/
│  └─ MyPluginFeature.cs
├─ Startup/
│  ├─ StartUpApplication.cs
│  └─ StartUpFeature.cs
├─ UI/
│  ├─ Views/
│  └─ ViewModels/
├─ Licensing/
│  └─ TekniqDeveloperInfo.cs
├─ Tools/
│  └─ TekniqSignLocal.exe
└─ MyPlugin.csproj

Why this helps

• Startup logic stays easy to find
• UI and application logic remain separate
• Licensing setup stays explicit
• Features can grow without turning the project into one large plugin class