Bug 33487 - 'CS1591' is not a valid warning number (CS1904)
Summary: 'CS1591' is not a valid warning number (CS1904)
Alias: None
Product: Compilers
Classification: Mono
Component: C# (show other bugs)
Version: unspecified
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Marek Safar
Depends on:
Reported: 2015-08-29 09:31 UTC by grokys
Modified: 2017-01-17 14:08 UTC (History)
2 users (show)

See Also:
Is this bug a regression?: ---
Last known good build:


Description grokys 2015-08-29 09:31:01 UTC
I'm using mono 4.2 from the alpha channel.

When compiling https://github.com/grokys/Perspex/ (commit 845b28a2c2ce858786bb11e1aa413916b2bb061d) in monodevelop I get the error:

    'CS1591' is not a valid warning number (CS1904)
Comment 1 Marek Safar 2015-08-31 08:17:07 UTC
Fixed in master and next 4.2 alpha
Comment 2 grokys 2016-02-18 18:47:33 UTC
This appears to still be a problem in 4.2.2:

targets (CoreCompile target) ->

    CSC: error CS1904: `CS1591' is not a valid warning number

     0 Warning(s)
     1 Error(s)
Comment 3 Marek Safar 2016-02-19 16:28:23 UTC
This fix is still only available in master and Mono 4.3.2 previews
Comment 4 Jamie Lord 2017-01-17 14:08:54 UTC
I'm currently experiencing the same thing with an up-to-date version of Xamarin and the latest version of Mono (4.6.2).

Is there any way to resolve this?

Notice (2018-05-21): bugzilla.xamarin.com will be switching to read-only mode on Thursday, 2018-05-25 22:00 UTC.

Please join us on Visual Studio Developer Community and GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs and copy them to the new locations as needed for follow-up. The See Also field on each Bugzilla bug will be updated with a link to its new location when applicable.

After Bugzilla is read-only, if you have new information to add for a bug that does not yet have a matching issue on Developer Community or GitHub, you can create a follow-up issue in the new location. Copy and paste the title and description from this bug, and then add your new details. You can get a pre-formatted version of the title and description here:

In special cases you might also want the comments:

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Note You need to log in before you can comment on or make changes to this bug.