Bug 19032 - System.Linq.Expressions.Expression: Constructors do not Match .NET/Mono
Summary: System.Linq.Expressions.Expression: Constructors do not Match .NET/Mono
Status: RESOLVED FIXED
Alias: None
Product: iOS
Classification: Xamarin
Component: XI runtime ()
Version: 7.2.0
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2014-04-14 10:07 UTC by Joe Pro
Modified: 2014-04-14 10:28 UTC (History)
3 users (show)

Tags:
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 Developer Community or GitHub 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:
Status:
RESOLVED FIXED

Description Joe Pro 2014-04-14 10:07:37 UTC
To illustrate the issue, let's define a very simple class that derives from Expression:

public class TestExpression : Expression {
}

When compiling against Xamarin.iOS, this will result in Error CS1729: The type `System.Linq.Expressions.Expression' does not contain a constructor that takes `0' arguments (CS1729).
However, it compiles just fine on Mono/.NET 4.0 and 4.5

Futhermore, the Expression(ExpressionType, Type) constructor should be obsolete as per: http://msdn.microsoft.com/en-us/library/system.linq.expressions.expression(v=vs.100).aspx

This bug is keeping me from running a few PCLs.


=== Xamarin Studio ===

Version 4.2.3 (build 60)
Installation UUID: 7919fd95-038c-4ab2-a2e5-c816c4e7b5f3
Runtime:
	Mono 3.2.6 ((no/9b58377)
	GTK+ 2.24.23 theme: Raleigh
	GTK# (2.12.0.0)
	Package version: 302060000

=== Xamarin.Android ===

Not Installed

=== Apple Developer Tools ===

Xcode 5.1.1 (5085)
Build 5B1008

=== Xamarin.Mac ===

Xamarin.Mac: Not Installed

=== Xamarin.iOS ===

Version: 7.2.0.2 (Business Edition)
Hash: 58c3efa
Branch: 
Build date: 2014-10-03 18:02:26-0400

=== Build Information ===

Release ID: 402030060
Git revision: 30c4afc300c2a39ec5300851357ce02e49dd217e
Build date: 2014-03-05 22:09:33+0000
Xamarin addins: f8a9589b57c2bfab2ccd73c880e7ad81e3ecf044

=== Operating System ===

Mac OS X 10.9.2
Darwin Josephs-Mac-mini.local 13.1.0 Darwin Kernel Version 13.1.0
    Thu Jan 16 19:40:37 PST 2014
    root:xnu-2422.90.20~2/RELEASE_X86_64 x86_64
Comment 1 Sebastien Pouliot 2014-04-14 10:28:53 UTC
This is already fixed in 7.2.1 [1] which is already in beta.

[1] http://docs.xamarin.com/releases/ios/xamarin.ios_7/xamarin.ios_7.2/#1