Bug 19095 - Inconsistent warning behaviour
Summary: Inconsistent warning behaviour
Alias: None
Product: Compilers
Classification: Mono
Component: C# ()
Version: 3.2.x
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Marek Safar
Depends on:
Reported: 2014-04-16 16:00 UTC by Allie Miller
Modified: 2014-04-29 12:45 UTC (History)
2 users (show)

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

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

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.

Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Allie Miller 2014-04-16 16:00:20 UTC
*Reported on behalf of a user*

With a project set to Warning Level 4 and 'Treat All Warnings as Errors', a public event that is never called results in different behaviors in Visual Studio vs. Xamarin Studio (on Mac). With Visual Studio, the unused event triggers a warning that's treated as an error. In Xamarin Studio on Windows, the used event is triggered as a warning that's treated as an error.  However, Xamarin Studio on Mac OSX (4.2.3) produces no warning. 

Versioning information along with a test case to reproduce the issue attached.
Comment 2 Marek Safar 2014-04-29 12:45:44 UTC
Fixed in master