From: William L. <xfu...@gm...> - 2011-02-02 12:39:26
|
On Wed, Feb 2, 2011 at 2:25 AM, Matthijs ter Woord < mat...@gm...> wrote: > IL has remained unchanged since .NET 2.0. Extension methods are just > compiler metadata (1 single attribute, together with source compiler > support), LINQ are just extension methods with source compiler support, .net > 4.0 dynamic objects is all implemented using .net extension methods, so > might be something else.. > This may be true, but technically the AOT (especially in the 0.0.1 release) probably does not actually handle all normal IL operations. If the new features have caused older code which worked to expose something using any of these features, this could be the cause. One example is support for strings. I don't recall if full string support was present in 0.0.1 or not, but for a long time we had to specially craft our string constant usage to use an AOT-provided converter to an IntPtr so that strings could be used without the runtime being active. We later had much nicer string support but code like: string str = "hello world"; would typically cause an error from the AOT similiar to what you got. It certainly could be something else though. Let us know what you find out :-) Just sayin' PS: I CCed my original reply to the list and you sent a reply to that direct to the list. If you aren't already subscribed to the developers list, you will likely want to sign up from sourceforge (sharpos.sf.net). |