The 3.0 release use a mono wrapper that replace the old script-based
launcher and the native library. If I recall well, you are using custom
build process, so you have to update it to use the new wrapper:
- The mono wrapper binary can be found in the "dist/10.x" folder of the
distribution. It is named "runtime".
- Copy it to the MacOS folder of the application bundle and rename it to
match the application bundle name.

As for the Ids returned instead of proper object, can you send me a list so
I can fix the wrapper generator ?

Regards, Laurent Etiemble.

2011/3/18 marc hoffman <m...@elitedev.com>

> Hi,
> i'm trying to migrate a Monobjc 2 to v3, because im seeing weird crashes
> under Mono 2.10, and not sure if those are caused by using an old Monobjc.
> in any case, i made all the changes to the code to reflect the new APIs
> (not a step forward imho btw, most of the changes i had to make were extra
> casts for places were Id is being returned instead of the proper object. i'm
> disappointed), but when i run, i get this error:
> Unhandled Exception: System.TypeInitializationException: An exception was
> thrown by the type initializer for Monobjc.ObjectiveCRuntime --->
> System.EntryPointNotFoundException: monobjc_install_bridge
>  at (wrapper managed-to-native) Monobjc.NativeMethods:InstallBridge ()
>  at Monobjc.ObjectiveCRuntime..cctor () [0x00000] in <filename unknown>:0
>  --- End of inner exception stack trace ---
>  at CocoaApplication1.Program.Main () [0x00000] in <filename unknown>:0
> (the proper dylib is deployed next to the startup binary)
> what could i be missing?

Reply via email to