Your tips got me to the root of the problem. The DLL name was missing a character from when I created the Android version of the Windows Phone project.
*facepalm* Thanks for your help. Steve 'Sly' Williams On 13 February 2012 11:41, Brannon King <[email protected]> wrote: > > Is there any trick or extra bit I should be doing in order to instantiate >> a class from another assembly? >> > > Did you try loading the assembly directly with a call to > Assembly.LoadFrom("Game.Data.dll") ? And I assume Game.Data.dll is the GAC > or the same path as your executable? Assuming the assembly does load, you > might try printing out the list of types from assembly.GetTypes() to see if > the type you're trying to load really does exist there. Another thing to do > is add event handlers to AppDomain.Current.TypeResolve/AssemblyResolve and > see what goes through them on your call. Do you possibly have multiple > versions of that DLL floating around? Sometimes there will be an old file > hanging around that gets loaded. Assembly.Location might help you in that > situation. > > _______________________________________________ > Monodroid mailing list > [email protected] > > UNSUBSCRIBE INFORMATION: > http://lists.ximian.com/mailman/listinfo/monodroid > >
_______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
