Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Incorrect error codes reported

See original GitHub issue

Version Used:

I’m updating Windows Forms SDK/toolset from P6 to RC1, and our builds fail with errors which we have already suppressed. E.g.:

It appears instead of CS0618 we must now be suppressing SYSLIB0011 but I had to spend time to figure it out on my own. Likewise we have other failures, e.g. …and only VS is telling me that I now need to suppress a different one:

Few builds:

Steps to Reproduce:

Clone this commit: https://github.com/dotnet/winforms/commit/2427ee0140db52050535e9459384e6527610720d
Run .\build.cmd
Observe multiple failures

Expected Behavior:

Errors must either correctly report codes or use the existing suppression rules.

Issue Analytics

State:
Created 3 years ago
Comments:25 (25 by maintainers)

Top GitHub Comments

1reaction

RikkiGibsoncommented, Sep 17, 2020

/+warnaserror seems to be the problem. The minimal repro project https://github.com/dotnet/roslyn/issues/47736#issuecomment-693708428 gives an unexpected error CS0618 when either <WarningsAsErrors>SYSLIB0011</WarningsAsErrors> is specified or <TreatWarningsAsErrors>true</TreatWarningsAsErrors> is specified.

Thanks to @jmarolf for helping me track this down. I suppose this bug didn’t have the chance to negatively impact more people since corefx didn’t add custom diagnostic IDs until recently.

1reaction

RussKiecommented, Sep 17, 2020

One thing I totally forgot to mention (sorry), to start Windows Forms solution in VS you need to run: