- 필수 기능
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- 디지털 경험
- 소프트웨어 제공
- 보안
- 로그 관리
- 관리
- 인프라스트럭처
- ci
- containers
- csm
- ndm
- otel_guides
- overview
- slos
- synthetics
- tests
- 워크플로
ID: csharp-best-practices/objects-ensure-use
Language: C#
Severity: Info
Category: Best Practices
Creating an object and then not using it can lead to unexpected behavior if the constructor contains side effects.
If the code intentionally creates and drops an object to trigger the constructor side effects, consider moving them to a separate function and call it directly.
class MyClass {
public void myMethod()
{
new MyClass();
}
}
class MyClass {
public void myMethod()
{
var obj = new MyClass();
}
}
|
|
For more information, please read the Code Analysis documentation
Identify code vulnerabilities directly in yourVS Code editor
Identify code vulnerabilities directly inJetBrains products