Template pack for building DisCatSharp-based .NET applications.
| Template | Short name | What it creates |
|---|---|---|
| DisCatSharp Bot Template | DCSBot |
A bot class library intended to be hosted by another app |
| DisCatSharp Solution Template | DCSSolution |
An ASP.NET Core host plus a bot project in one .slnx solution |
| DisCatSharp Web App Template | DCSWebApp |
An ASP.NET Core host |
dotnet new install DisCatSharp.ProjectTemplatesCreate the bot class library:
dotnet new DCSBot -n MyBot --DiscordToken "DISCORD_TOKEN"Create the hosted solution:
dotnet new DCSSolution -n MyBot --DiscordToken "DISCORD_TOKEN"Create the web app host:
dotnet new DCSWebApp -n MyWebHostTo see the full parameter list for either template:
dotnet new DCSBot --help
dotnet new DCSSolution --help
dotnet new DCSWebApp --helpThe bot and solution templates support these DisCatSharp module switches:
--UseApplicationCommands--AddTranslations(requires--UseApplicationCommands)--UseCommandsNext--UseCommon--UseInteractivity--UseLavalink--UseVoice--UseVoiceNatives
The standalone DCSWebApp template is just the ASP.NET Core host shell, so it intentionally has no custom template options.
The bot settings file uses the current nested DiscordConfiguration model. The generated DisCatSharpProjectBot.settings.json includes:
TokenIntentsGatewayCacheLogging
This matches the modern DisCatSharp configuration structure and keeps gateway/cache/logging settings clearly separated.
- The solution template generates an
.slnxsolution file. - Rider still has limited support for custom template parameters, so command-line usage is the safest path when you need template options.