locked
[UWP]Win10 SDK Runtime component error: Windows.Foundation.Point

    Question

  • The actual error is: Windows Runtime type 'Windows.Foundation.Point' was found in multiple referenced winmd files. WINMDEXP.

    The project is a simple Windows Universal Runtime Component which is being referenced in a UWP app.

    To reproduce:

    1. File > New Windows Universal (UAP,Version=10.0.10069.0)
    2. Add a new project, of type Windows Runtime component and reference it from the UWP
    3. Add the Lumia Imaging SDK v2.2.208 to the RuntimeComponent
    4. Build the solution

    You will get the error I list above (you may also notice there is a bug that builds both projects even if you try to build only the RuntimeComponent project by itself).

    Update: I discovered a strange quirk... If I change the project to debug/x86 and build as a ClassLibrary, it will build. Then if I change back to a RuntimeComponent immediately afterwards, it will build. This doesn't work every time however, which you will

    Thanks!


    Lance W. McCarthy Windows Phone Developer



    Sunday, May 3, 2015 10:52 PM

Answers

  • The version of the SDK installed through Nuget is not supported for Windows 10 development.   It is great you hacked it into your project, but it is not supported.  Proceed at your own risk.

    There have been a lot of updates to the built in Windows 10 Imaging SDK.  I suggest using that until there is a version of the Lumia Imaging SDK that supports Windows 10.


    Bret Bentzinger (MSFT) @awehellyeah

    Monday, May 11, 2015 3:45 PM
    Moderator

All replies

  • How are you adding the Lumia Imaging SDK? I don't see a version of that SDK that supports UWP's. That is most likely the issue. Remove that, and the project should build.

    If you do have a version that supports UWP's, where did you get it? I can then try again and open a bug.


    Bret Bentzinger (MSFT) @awehellyeah

    Wednesday, May 6, 2015 6:49 PM
    Moderator
  • The SDK is acquired through Nuget, which lets you add it in strangely enough. However, I have been able to get it to work by doing the following:

    1- change RuntimeComponent build action to be a ClassLibrary

    2- change it back to RuntimeComponent

    aaaand it works! I have no idea why it does, but it does.

    To save you some time, here is a link to download the working example. Go to the ExampleEffectLibrary RuntimeComponent project and you'll see that it uses the Imaging SDK and my GrayscaleVideoEffect.cs class uses it.

    (Note: The sample is based on Jason Olson's Media Editing example from Build 2015. There's a separate, unrelated, bug (which he is aware of), but the project demonstrates that it can work after making the above changes.


    Lance W. McCarthy Windows Phone Developer


    • Edited by LanceMcCarthyMVP Wednesday, May 6, 2015 7:28 PM spelling correction and clarification on last sentence
    Wednesday, May 6, 2015 7:27 PM
  • The version of the SDK installed through Nuget is not supported for Windows 10 development.   It is great you hacked it into your project, but it is not supported.  Proceed at your own risk.

    There have been a lot of updates to the built in Windows 10 Imaging SDK.  I suggest using that until there is a version of the Lumia Imaging SDK that supports Windows 10.


    Bret Bentzinger (MSFT) @awehellyeah

    Monday, May 11, 2015 3:45 PM
    Moderator
  • Thanks Bret, that solves the issue.

    Regarding your recommendation, do you mean Win2D when you say "Windows 10 Imaging SDK"?


    Lance W. McCarthy Windows Phone Developer

    Monday, May 11, 2015 3:57 PM