Christopher Felegy 497918edda fix: raise CommandExecuted on async errors
This resolves #1224.

Previously, raising CommandExecuted for errors was dependent on the
failed result making it back to ExecuteAsync. This is not possible with
async commands, which always pass back a succesful promise result,
rather than their fulfilled result.

This change moves the event invocation for exception'd ExecuteResults to
their source, and excludes ExecuteResult from the late event invocation
in CommandService#ExecuteAsync.
2018-12-31 13:36:30 -05:00
2018-12-20 17:22:57 -05:00
2018-09-30 17:44:33 -04:00
2018-01-06 22:30:04 -05:00
2015-08-09 11:36:55 -03:00
2018-12-28 21:29:34 -05:00
2018-09-30 17:44:33 -04:00
2017-07-14 15:31:30 -03:00
2018-08-20 18:27:50 -04:00

Discord.Net

NuGet MyGet Build status Discord

An unofficial .NET API Wrapper for the Discord client (http://discordapp.com).

Check out the documentation or join the Discord API Chat.

Installation

Stable (NuGet)

Our stable builds available from NuGet through the Discord.Net metapackage:

The individual components may also be installed from NuGet:

Unstable (MyGet)

Nightly builds are available through our MyGet feed (https://www.myget.org/F/discord-net/api/v3/index.json).

Compiling

In order to compile Discord.Net, you require the following:

Using Visual Studio

The .NET Core workload must be selected during Visual Studio installation.

Using Command Line

Known Issues

WebSockets (Win7 and earlier)

.NET Core 1.1 does not support WebSockets on Win7 and earlier. This issue has been fixed since the release of .NET Core 2.1. It is recommended to target .NET Core 2.1 or above for your project if you wish to run your bot on legacy platforms; alternatively, you may choose to install the Discord.Net.Providers.WS4Net package.

Languages
C# 100%