Problems running under MonoTouch

[mikeorb]

I can run my test code fine under the iOS simulator, but run into JIT
issues when running on real device. I created a small project with
only mapping to ensure that the error was not from something else. I
used the sample classes and MT alternative mapping syntax:

Domain.Configure
(
Map.Entity<Person>()
.Table("Users")
.Map(new ValuePropertyMap<Person, string>(x =>
x.FirstName))
.Map(new ValuePropertyMap<Person, string>(x =>
x.LastName)),
Map.Entity<Forum>()
.Map(new ValuePropertyMap<Forum, string>(x => x.Name))
.Map(new ListPropertyMap<Forum, Post>(x => x.Posts, true)),
Map.Entity<Post>()
.ParentColumn("ForumId")
.Map(new ValuePropertyMap<Post, string>(x => x.Title))
.Map(new ValuePropertyMap<Post, string>(x => x.Body))
.Map(new BelongsToPropertyMap<Post, Person>(x => x.Poster,
"PosterId"))
);

The error I get is:

Attempting to JIT compile method
System.Linq.Expressions.ParameterExpression:.ctor(System.Type,string)'
while running with --aot-only
at System.Linq.Expressions.Expression.Parameter(System.Type type,
System.String name)

The project is at:

http://orb.dreamhost.com/xfer/catnap.tar.gz

This is with MonoTouch 4.2 and MonoDevelop 2.8. I have not tried
earlier releases.

Any advice? I am stuck but was liking Catnap very much.

Thanks,
-Mike

[Tim Scott]

Mike,

Unfortunately I cannot do much right now to help you solve it. I recently upgraded to Lion, and now my MT environment is dead. I cannot compile any MT code with the current version of MT, and the new version is not supported by my license. That's right, I have to buy a $250 upgrade from Xamarin to even compile my existing code. In fact, today I discovered that I can't even open my existing solutions in the latest version of MD. I haven't done MT development for a while, so I'm not eager to spend the time and money right now. I'll probably bite the bullet and untangle this mess, but for now I'm dead.

The error you are getting is one that I have seen before. I reported it to Novell, maybe a couple of years ago, and they fixed it. I'd bet that MT has simply regressed. Here's what I suggest. Submit a bug report to Xamarin and attach your solution as a repo sample. In that past they have been attentive in most cases (although they stopped short of getting the simpler mapping syntax to work). Since Xamarin is the same team, you might get a good result.

Just yesterday someone asked my about MT dev experience. I told them MT is great, a real achievement, but there are a lot of sharp edges! This is a good example.

Cheers,
Tim

[Mike Orb]

Hey Tim. I hear you about MT. I hope Xamarin has turned the corner with the Novell license. I am listening to a presentation from their recent Monospace conference as I type this. They have 25 employees and are starting to really improve the product again. I am just doing a hobby project -- I develop C# desktop apps in my day job -- and was close to abandoning MT in favor of Objective C. But think MT will really start to take off now, if only because of Enterprise use.

I will submit a ticket to Xamarin and let everyone know.

Do you recall what version of MD and MT you previously used with success? I'd like to try downgrading my MD/MT versions.

Thanks so much for getting back to me!

Cheers,
-Mike

[Tim Scott]

I think it's 3.2.6 of MT. I don't know exactly how to see what version is currently installed. As far as MD, I'm think it was probably 2.4.1.

On Sunday, September 11, 2011 at 8:13 PM, Mike Orb wrote:

> Hey Tim. I hear you about MT. I hope Xamarin has turned the corner with the Novell license. I am listening to a presentation (http://www.infoq.com/presentations/QA-on-Mono) from their recent Monospace conference as I type this. They have 25 employees and are starting to really improve the product again. I am just doing a hobby project -- I develop C# desktop apps in my day job -- and was close to abandoning MT in favor of Objective C. But think MT will really start to take off now, if only because of Enterprise use.

>
> I will submit a ticket to Xamarin and let everyone know.
>
> Do you recall what version of MD and MT you previously used with success? I'd like to try downgrading my MD/MT versions.
>
> Thanks so much for getting back to me!
>
> Cheers,
> -Mike
>

[Mike Orb]

A while back I created a ticket with Xamarin and they marked it as duplicate of:

http://bugzilla.xamarin.com/show_bug.cgi?id=770

This was was recently closed as fixed in next release :-).

-Mike

[Tim Scott]

Awesome! I was thinking I might rekindle my MT development. This takes one headache out of that process!

[mikeorb]

I installed the latest MonoTouch -- 4.2.2 -- and yay my Catnap code is
finally working on a real device. Note I still have to use the more
explicit mapping style code documented by Tim.

Cheers,
-Mike

[Tim Scott]

Thanks for running down that rabbit!

On Thursday, September 29, 2011 at 9:20 PM, mikeorb wrote:

> I installed the latest MonoTouch -- 4.2.2 -- and yay my Catnap code is
> finally working on a real device. Note I still have to use the more
> explicit mapping style code documented by Tim.
>
> Cheers,
> -Mike
>