Update config elsewhere #13
Annotations
10 errors and 10 warnings
Source/Twitch/Client.cs#L86
'Message' does not contain a definition for 'IsFromSystem' and no accessible extension method 'IsFromSystem' accepting a first argument of type 'Message' could be found (are you missing a using directive or an assembly reference?)
|
Source/Twitch/Client.cs#L86
'Command' does not contain a definition for 'Welcome'
|
Source/Twitch/Client.cs#L87
'Message' does not contain a definition for 'IsFromSystem' and no accessible extension method 'IsFromSystem' accepting a first argument of type 'Message' could be found (are you missing a using directive or an assembly reference?)
|
Source/Twitch/Client.cs#L99
'Command' does not contain a definition for 'Join'
|
Source/Twitch/Client.cs#L102
'Message' does not contain a definition for 'IsAboutUser' and no accessible extension method 'IsAboutUser' accepting a first argument of type 'Message' could be found (are you missing a using directive or an assembly reference?)
|
Source/Twitch/Client.cs#L102
'Command' does not contain a definition for 'Join'
|
Source/Twitch/Client.cs#L116
'Message' does not contain a definition for 'IsFromSystem' and no accessible extension method 'IsFromSystem' accepting a first argument of type 'Message' could be found (are you missing a using directive or an assembly reference?)
|
Source/Twitch/Client.cs#L116
'Command' does not contain a definition for 'YourHost'
|
Source/Twitch/Client.cs#L123
The name 'ExpectedHost' does not exist in the current context
|
Source/Twitch/Client.cs#L124
The name 'ExpectedHost' does not exist in the current context
|
Source/Shared.cs#L24
'SslProtocols.Tls' is obsolete: 'TLS versions 1.0 and 1.1 have known vulnerabilities and are not recommended. Use a newer TLS version instead, or use SslProtocols.None to defer to OS defaults.' (https://aka.ms/dotnet-warnings/SYSLIB0039)
|
Source/Shared.cs#L25
'SslProtocols.Tls11' is obsolete: 'TLS versions 1.0 and 1.1 have known vulnerabilities and are not recommended. Use a newer TLS version instead, or use SslProtocols.None to defer to OS defaults.' (https://aka.ms/dotnet-warnings/SYSLIB0039)
|
Source/Program.cs#L181
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
Source/Program.cs#L233
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
Source/Program.cs#L238
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
Source/Program.cs#L255
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
Source/Program.cs#L260
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
Source/Program.cs#L277
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
Source/Program.cs#L282
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
Source/Program.cs#L287
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
The logs for this run have expired and are no longer available.
Loading