Skip to main content

MonoTouch - type load exception, updated program not registered in simulator



I've installed trial version of MonoTouch, and I'm evaluating it for use.





This strange error has occurred:







Could not load 'MyProductName' for registration. This could be due to an outdated assembly kept by the simulator, location: /PathToMyProduct







Followed by:







A type load exception has occurred.







My guess is that, somehow some assembly is not up to date. So I've tried to remove it from the given path. But still it's there. So I performed a purge (reinstalled MonoTouch, removed binary build path, in simulator path, uninstalled from simulator, reset simulator, and finally restarted the OSX). But still it's there.





Any hints on how to solve this peculiar problem?





regards, Kate


Comments

  1. That message covered most of the cases where such an exception occurred. This was fixed (actually we worked around the simulator bug) in MonoTouch 5.0+ (even earlier but I don't recall exactly which version). Simply resetting the simulator is enough to fix this condition.

    However this is unlikely the situation you're facing since you did a lot more than what would have been required.

    My guess would be that the project includes an assembly that refers to types that are not available in MonoTouch (e.g. from System.Reflection.Emit) or compiled against a different version of the framework (e.g. reusing an assembly binary compiled against .NET 4.0). However both cases do not generally lead to this error message so it could be something else.

    It will be hard to further diagnose the problem without having the binaries. Could you either open a bug report on http://bugzilla.xamarin.com (you can mark the attachment as private) or send an email to support@xamarin.com (with the project attached) ?

    ReplyDelete

Post a Comment

Popular posts from this blog

Slow Android emulator

I have a 2.67 GHz Celeron processor, 1.21 GB of RAM on a x86 Windows XP Professional machine. My understanding is that the Android emulator should start fairly quickly on such a machine, but for me it does not. I have followed all instructions in setting up the IDE, SDKs, JDKs and such and have had some success in staring the emulator quickly but is very particulary. How can I, if possible, fix this problem?

CCNA 3 Final Exam => latest version

1 . Which security protocol or measure would provide the greatest protection for a wireless LAN? WPA2 cloaking SSIDs shared WEP key MAC address filtering   2 . Refer to the exhibit. All trunk links are operational and all VLANs are allowed on all trunk links. An ARP request is sent by computer 5. Which device or devices will receive this message? only computer 4 computer 3 and RTR-A computer 4 and RTR-A computer 1, computer 2, computer 4, and RTR-A computer 1, computer 2, computer 3, computer 4, and RTR-A all of the computers and the router   3 . Refer to the exhibit. Hosts A and B, connected to hub HB1, attempt to transmit a frame at the same time but a collision occurs. Which hosts will receive the collision jamming signal? only hosts A and B only hosts A, B, and C only hosts A, B, C, and D only hosts A, B, C, and E   4 . Refer to the exhibit. Router RA receives a packet with a source address of 192.168.1.65 and a destination address of 192.168.1.161...