Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Created attachment 4531 [details]
Test case, failure
Related to bug 13324, and bug 13289, but this case still fails in the latest Mono master off GitHub, assuming I compiled it properly :)
Switching the order of the Compile Include lines in a project file can cause compilation errors if one part of a partial class has a base class while another does not.
## Steps to reproduce
1. Open the TestCaseSuccess or TestCaseFailure project in Xamarin Studio on Mac.
The TestCaseFailure project fails. Adding the base class at ReportServiceClient.iOS.cs:10 also works around the problem:
`partial class ReportServiceClient : ClientBase<IReportService>`
On the command line, this fails:
mcs /t:library /out:Test.dll /r:System.Servicemodel ReportServiceClient.iOS.cs ReportServiceClient.cs
And this succeeds:
mcs /t:library /out:Test.dll /r:System.Servicemodel ReportServiceClient.cs ReportServiceClient.iOS.cs
## Expected Result
The order of the "Compile Include" lines should not matter.
Created attachment 4532 [details]
Test case, success
Fixed in master