Windows Phone 7 and MissingMethodException

by Geert 27. August 2011 13:44

Recently I was building a demo application for Windows Phone 7 to show how it can be used with Catel. I created a new Windows Phone 7 project (for Mango) and tried to run the example. I hit a strange exception when a view model was constructed:

Now I thought: WTF?! I am pretty sure that this method exists, and the same code works for WPF, Silverlight and Windows Phone 7 (non-mango). After a few hours and trying, I decided to comment out the content of the RegisterViewModelServices method. What seemed: it’s the content of the method responsible for the MissingMethodException.

Let’s take a look at the content of that method:

/// <summary>

/// Registers the known view model services.

/// </summary>

/// <param name="serviceLocator">The service locator.</param>

protected override void RegisterViewModelServices(IServiceLocator serviceLocator)

{

    // Logger already created, no IoC required

    if (!_injectedServices.ContainsKey(typeof(ILogger)))

    {

        _injectedServices.Add(typeof(ILogger), Log);

    }

  

    try

    {

        Log.Debug(TraceMessages.RegisteringDefaultServiceImplementationsForIoCContainer);

  

#if WINDOWS_PHONE

        serviceLocator.RegisterTypeIfNotYetRegistered<ILocationService, LocationService>();

        serviceLocator.RegisterTypeIfNotYetRegistered<IMessageService, MessageService>();

        serviceLocator.RegisterTypeIfNotYetRegistered<INavigationService, Services.NavigationService>();

        serviceLocator.RegisterTypeIfNotYetRegistered<IVibrateService, VibrateService>();

#if WINDOWS_PHONE_MANGO

        serviceLocator.RegisterTypeIfNotYetRegistered<IAccelerometerService, AccelerometerService>();

        serviceLocator.RegisterTypeIfNotYetRegistered<ICameraService, CameraService>();

        serviceLocator.RegisterTypeIfNotYetRegistered<ICompassService, CompassService>();

        serviceLocator.RegisterTypeIfNotYetRegistered<IGyroscopeService, GyroscopeService>();

#endif

#elif SILVERLIGHT

        serviceLocator.RegisterTypeIfNotYetRegistered<IMessageService, MessageService>();

        serviceLocator.RegisterTypeIfNotYetRegistered<INavigationService, NavigationService>();

        serviceLocator.RegisterTypeIfNotYetRegistered<IOpenFileService, OpenFileService>();

        serviceLocator.RegisterTypeIfNotYetRegistered<IPleaseWaitService, PleaseWaitService>();

        serviceLocator.RegisterTypeIfNotYetRegistered<ISaveFileService, SaveFileService>();

        serviceLocator.RegisterTypeIfNotYetRegistered<IUIVisualizerService, UIVisualizerService>();

#else // WPF

        serviceLocator.RegisterTypeIfNotYetRegistered<IMessageService, MessageService>();

        serviceLocator.RegisterTypeIfNotYetRegistered<INavigationService, NavigationService>();

        serviceLocator.RegisterTypeIfNotYetRegistered<IOpenFileService, OpenFileService>();

        serviceLocator.RegisterTypeIfNotYetRegistered<IPleaseWaitService, PleaseWaitService>();

        serviceLocator.RegisterTypeIfNotYetRegistered<IProcessService, ProcessService>();

        serviceLocator.RegisterTypeIfNotYetRegistered<ISaveFileService, SaveFileService>();

        serviceLocator.RegisterTypeIfNotYetRegistered<IUIVisualizerService, UIVisualizerService>();

#endif

  

        Log.Debug(TraceMessages.RegisteredDefaultServiceImplementationsForIoCContainer);

    }

    catch (Exception ex)

    {

        Log.Error(ex, TraceMessages.FailedToConfigureIoCContainer);

  

        throw new Exception(Exceptions.FailedToConfigureIoCContainer, ex);

    }

}

As you can see, all services that should be available per platform are registered so the user doesn’t have to do this. After commenting out all services and adding them one by one, it seems that all services regarding sensors were causing the MissingMethodException.

Then I thought: hey, they all share a common base class, maybe something is wrong with the base class for sensor services. After checking out all the references, it seems the following were referenced in Catel, but not in the demo app:

mscorlib.Extensions
Microsoft.Devices.Sensors
Microsoft.Xna.Framework
System.Device
System.Runtime.Serialization
System.Xml.Linq

I decided to add them all, even though I knew that those references should be included automatically (or at least be available since they are part of the phone framework). Again, no luck, still got the MissingMethodException.

At this time, I was already bald because I pulled all my hair out…

I double checked all references and made sure they were all pointing to the same files (right version, right runtime, etc). Still no luck.

Then I thought: hey, I did change something in the ISensorService recently. Instead of this definition:

public interface ISensorService<TValueInterface, TEventArgs> 

    where TEventArgs : EventArgs

I used this definition:

public interface ISensorService<out TValueInterface, TEventArgs> 

    where TEventArgs : EventArgs

I added the out because ReSharper told me I could define it as covariant. What seems: changing it back to a non-covarient type parameter solves the issue.

Now I am still now sure: is this a bug in my code, or is it a bug in the runtime? If you know, please let me know!

8be07c70-86da-4c1b-89ab-c5b11e6bb9b2|0|.0

Tags: wp7

C# | Windows Phone 7

Sneak preview: Catel and support for Windows Phone 7 MangoSince version 1.4, Catel fully supports the MVVM implementation of Catel for Windows Phone 7. Just a...Getting geographic locations on Windows Phone 7 and MVVMWe heard a lot about Windows Phone 7. We also heard a lot about MVVM. But lately I was wondering: ho...Navigation for Windows Phone 7 using MVVMWhile we were working on the support for Windows Phone 7 in Catel, we encountered a complex problem ...

Comments (1) -

Andrey

9/13/2011 9:46:47 PM #

Hi, I have the same problem exactly, if I make any parameter covariant or even have any field with covariant interface it throws exception and doesn't load dll.
That killed two days for me. :-(
I even couldn't think about such possibility.

Pingbacks and trackbacks (1)+

Comments are closed

Windows Phone 7 and MissingMethodException

Comments (1) -

Pingbacks and trackbacks (1)+

Twitter

About the Author

Windows Phone 7 and MissingMethodException

Comments (1) -

Pingbacks and trackbacks (1)+

Twitter

BlogRoll

Tag cloud

About the Author