dotnet/roslyn

VS2022 TreatWarningsAsErrors resolved analyzer IDE0059

Open

#57,610 opened on Oct 31, 2021

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)C# (4,257 forks)batch import
Area-AnalyzersBugDeveloper CommunityFeature - IDE0059help wanted

Repository metrics

Stars
 (20,414 stars)
PR merge metrics
 (Avg merge 6d 17h) (256 merged PRs in 30d)

Description

This issue has been moved from a ticket on Developer Community.

I changed the CSPROJ to treat warnings as errors. Afterward Visual Studio updated and the warnings shown in the Errors window disappeared as-if they were resolved

https://user-images.githubusercontent.com/9797472/139598205-9f7e4f6b-1d90-4d5f-9f34-83f2b64db091.mp4

Original Comments

Feedback Bot on 10/28/2021, 08:06 PM:

Feedback Bot on 10/29/2021, 10:20 AM:

Original Solutions

(no solutions)

Contributor guide

Research direction
Investigate how TreatWarningsAsErrors in CSPROJ affects the display of analyzer warnings in Visual Studio error list.
Tech stack
csharp
Domain
developer experience
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
C#
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60