Search Unity

  1. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  2. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

Catastrophic failure - Mono.Cecil.AssemblyResolutionException

Discussion in 'Windows' started by Default117, Sep 29, 2013.

  1. Default117

    Default117

    Joined:
    Mar 13, 2011
    Posts:
    134
    Hey guys, i'm having some issues writing a plugin for a Windows Store App. This plugin will have some basic functionality, i.e. storing and retrieving images from the pictures library as well listening for and handling window snapping.
    I made my 'fake' and 'real' DLL, and did some basic tests with very basic functions, it all works perfectly fine. I get errors however when i try to do more Windows specific things, in particular if i access things within the Windows namespace i get a compiler error:

    This is my 'real' DLL code:
    Code (csharp):
    1. using System;using System.Diagnostics;
    2.  
    3.  
    4. namespace Win8Plugin
    5. {
    6.     public class Test
    7.     {
    8.         public static string TestFunction()
    9.         {
    10.             return Windows.Storage.KnownFolders.PicturesLibrary.DisplayName;
    11.         }
    12.     }
    13. }
    14.  
    I get the same error when i try to listen to the Windows.UI.Xaml.Window.Current.SizeChanged (again within the Window namespace) delegate, and implement the call back function.

    Am i doing something terribly wrong?
     
  2. Tomas1856

    Tomas1856

    Unity Technologies

    Joined:
    Sep 21, 2012
    Posts:
    3,875
    Hi, can you attach please Editor.log?
     
  3. Default117

    Default117

    Joined:
    Mar 13, 2011
    Posts:
    134
    Hi Tomas, heres the log file, had to zip it since *.log was not allowed. This was run from a completely clean project, just the plugin and a main scene.

    View attachment $Editor.zip
     
  4. Tomas1856

    Tomas1856

    Unity Technologies

    Joined:
    Sep 21, 2012
    Posts:
    3,875
    It seems you're using 4.3, which is not yet released, in that case, please use beta group instead.