locked
[Desktop Bridge][UWP] Including a uwp api from a Windows Application Packaging Project causes 9805 errors RRS feed

  • Question

  • I have a windows store WPF desktop bridge app compiled to 4.6.1. I am going to give the app away free and allow for in app purchases. To do this I need to use the UWP API for the windows store service.

    I am also using the new Windows Application Packaging Project template.

    I want to keep the UWP API separate from the WPF project, so I have created a serparate dll project for the UWP API. I reference System.Runtime.WindowsRuntime and Windows. Use basic code from the Store Sample.

    I add a reference from the WPF app to the UWP dll.

    As soon as I reference the UWP dll the desktop bridge packaging app will return 9805 Errors and 1 warning.

    One of the errors (which is typical) is

    The .winmd file 'Windows.winmd' contains type 'Windows.Gaming.Input.Gamepad'. The use of the Windows namespace is reserved.

    The warning is

    No implementation file was provided for the .winmd file 'OUTPUT DIRECTORY PATH\Windows.winmd'. To generate registration information in the app manifest, specify the 'Implementation' metadata on the .winmd reference item in the project file.

    I get the same errors if I add the two references to the WPF directly (System.Runtime.WindowsRuntime and Windows) and remove the UWP dll.

    I have also tried changing all the projects from 4.6.1 to 4.5.2.

    Anyone know what is going on?

    Tuesday, November 14, 2017 2:48 AM

Answers

  • Using the Windows.Services.Store namespace in a desktop bridge application is not compatible with the Windows Application Packaging Project. When building the packaging project, it will perform WACK tests which will throw 9805 errors and stop the creation of the appx bundle.

    Manually creating the package will still give you to 9805 errors if you perform the WACK tests. But at least you should have an appx you can submit to the store.
    • Marked as answer by hypodyne1 Friday, November 17, 2017 11:18 PM
    Friday, November 17, 2017 11:18 PM

All replies

  • Have confirmed this is a problem with Desktop Bridge by:

    • Creating a new WPF App project.
    • Creating a new Windows Application Packaging Project and configure it to include the WPF project.
    • Build the WPF project.
    • Create an appx package and perform WACK tests. All Okay.
    • Add a reference to the C:\Program Files (x86)\Windows Kits\10\UnionMetadata\winmd
    • Add a reference to the C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETCore\v4.5\System.Runtime.WindowsRuntime.dll
    • Build the WPF project.
    • Trying to build the Packaging Project results in 9805 errors.

    Here is the blog that I was following: https://blogs.windows.com/buildingapps/2017/01/25/calling-windows-10-apis-desktop-application/

    Tuesday, November 14, 2017 3:34 AM
  • Good News.

    The latest Visual Studio updates has fixed this issue. I am just left with the warning now.

    Thanks to who ever fixed it.

    Wednesday, November 15, 2017 12:58 AM
  • Hi

    Glad to hear that the problem is solved. You could mark your last reply as answer.

    This could help others who are facing the same problem.

    Best regards,

    Roy


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, November 15, 2017 5:40 AM
  • With further testing I have found the Windows Application Packaging Project does not allow you to add a reference to the store service API.

    This issue is still open.

    Friday, November 17, 2017 7:27 AM
  • Where do you report a bug to the Windows Application Packaging Project team?

    thanks

    Haydn

    Friday, November 17, 2017 7:30 AM
  • The Error Messages are coming from the WACK tests. Anyone know how to fix that?

    <TEST INDEX="54" NAME="Type name correctness" DESCRIPTION="Only system types can be in the Windows namespace and no types can be in the global namespace." EXECUTIONTIME="00h:00m:08s.46ms" OPTIONAL="FALSE">
            <MESSAGES>
              <MESSAGE TEXT="The Windows.ApplicationModel.StartupTaskState type in the Windows.winmd file is in the Windows namespace." />
              <MESSAGE TEXT="The Windows.ApplicationModel.PackageSignatureKind type in the Windows.winmd file is in the Windows namespace." />
              <MESSAGE TEXT="The Windows.ApplicationModel.PackageVersion type in the Windows.winmd file is in the Windows namespace." />

    Friday, November 17, 2017 10:38 PM
  • Using the Windows.Services.Store namespace in a desktop bridge application is not compatible with the Windows Application Packaging Project. When building the packaging project, it will perform WACK tests which will throw 9805 errors and stop the creation of the appx bundle.

    Manually creating the package will still give you to 9805 errors if you perform the WACK tests. But at least you should have an appx you can submit to the store.
    • Marked as answer by hypodyne1 Friday, November 17, 2017 11:18 PM
    Friday, November 17, 2017 11:18 PM