locked
Adding appointment capability in an UAP + CTP6

    Question

  • Is it possible to add the appointment capability in the appxmanifest and use the appointments api with the Windows 10 technical preview SDK or is it disabled in an UAP app?

    Here's how it's made in the WP8.1 but doesn't work in a Windows 10 UAP project. Tried also with different namespaces with no luck.

      <Capabilities>
        <m3:Capability Name="appointments" />
      </Capabilities>

    • Edited by Sandra_10 Tuesday, March 31, 2015 8:42 AM
    Monday, March 30, 2015 4:15 PM

Answers

  • Hi Sandra,

    I have filed a bug for this issue and it is being tracked. More information will be shared at //Build.

    Thanks,

    Prashant


    Windows Store Developer Solutions, follow us on Twitter: @WSDevSol|| Want more solutions? See our blog

    • Marked as answer by Sandra_10 Friday, April 10, 2015 12:36 PM
    Tuesday, April 7, 2015 5:03 PM
    Moderator

All replies

  • Which namespace did you try? For example if you create a Blank C# UAP app and then open the package.appxmanifest file - to see the XML code, you can add the following capability and the app will compile without any compilation errors:

    <Capabilities>
        <Capability Name="internetClient" />
        <uap:Capability Name="appointments" />
      </Capabilities>


    Windows Store Developer Solutions, follow us on Twitter: @WSDevSol|| Want more solutions? See our blog

    Tuesday, March 31, 2015 1:40 AM
    Moderator
  • Thanks Prashant!

    You've right it compiles without errors.
    Now my problem after that is that I can't use any of the appointment methods/classes.

    If I try this for example:
    Appointment appointment=new Appointment();

    It throws an exception:
    A first chance exception of type 'System.IO.FileNotFoundException' occured in App1.exe
    The specified module could not be found. (Exception from HRESULT: 0x8007007E)

    StackTrace: at System.StubHelpers.GetWinRTFactoryObject(IntPtr pCPCMD) at Windows.ApplicationModel.Appointment..ctor()
    • Edited by Sandra_10 Tuesday, March 31, 2015 8:45 AM
    Tuesday, March 31, 2015 8:42 AM
  • Thanks for clarifying and reporting the issue Sandra. I am investigating and will keep you updated.

    Windows Store Developer Solutions, follow us on Twitter: @WSDevSol|| Want more solutions? See our blog

    Thursday, April 2, 2015 7:18 PM
    Moderator
  • Thanks.
    Friday, April 3, 2015 12:11 PM
  • Hi Sandra,

    I have filed a bug for this issue and it is being tracked. More information will be shared at //Build.

    Thanks,

    Prashant


    Windows Store Developer Solutions, follow us on Twitter: @WSDevSol|| Want more solutions? See our blog

    • Marked as answer by Sandra_10 Friday, April 10, 2015 12:36 PM
    Tuesday, April 7, 2015 5:03 PM
    Moderator
  • I had the same issue as Sandra, but I did found a "temporary" work around so I could atleast continue working on the appointment/calendar feature in my application.

    Here's what I did to make the Appointment api work on the Windows 10 Preview SDK:
    1) Open the Package.appxmanifest file in your solution.
    2) Remove IgnorableNamespaces="uap mp" on the top to allow the uap namespace.
    3
    ) Add <uap:Capability Name="appointments" /> to <Capabilities> on the bottom.
    4) Build the application for your platform architecture... select "x64" if you are using a 64bit Windows installation... not "Any CPU".

    Hope this helps you out a bit... It worked for me on my PC (64bit), Tablet (32bit) and Phone (ARM).

    Greets,
    Arnold


    • Edited by Arnold Vink Tuesday, April 14, 2015 3:45 PM
    Tuesday, April 14, 2015 2:13 PM