- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
ID: csharp-best-practices/async-task-not-void
Language: C#
Severity: Error
Category: Best Practices
According to the task asynchronous programming (TAP) model, async methods should only return void
if they are event handlers. Otherwise, they should return Task
or Task<TResult>
class NonCompliant {
async void AsyncFetch() { /* ... */ }
async void Click() { /* ... */ }
async void HandleClick(object sender, EventArgs e, string notEventHandlerDelegateSignature) { /* ... */ }
}
using Microsoft.Extensions.Logging;
using Microsoft.Extensions.Logging.Abstractions;
namespace Gemini.Build.CodeGeneration
{
public class Logger : ILogger
{
public static ILogger Log { get; set; } = NullLogger.Instance;
void ILogger.Log<TState>(LogLevel logLevel, EventId eventId, TState state, Exception? exception, Func<TState, Exception?, string> formatter)
{
Log.Log(logLevel, eventId, state, exception, formatter);
}
public bool IsEnabled(LogLevel logLevel)
{
return Log.IsEnabled(logLevel);
}
public IDisposable BeginScope<TState>(TState state)
{
return Log.BeginScope(state);
}
}
}
class Compliant {
async Task AsyncFetch() { /* ... */ }
async void OnClick() { /* ... */ }
async void HandleClick(object sender, EventArgs e) { /* ... */ }
}
|
|
For more information, please read the Code Analysis documentation
Identify code vulnerabilities directly in yourVS Code editor
Identify code vulnerabilities directly inJetBrains products