Share via


CONTENT MOVED: Quickstart: Sending a Toast notification with custom audio

Content moved

Please see the article on docs.microsoft.com for the latest documentation.

Comments

  • Anonymous
    June 19, 2016
    Thanks for sharing this! Still gotta test it myself, haven't had the time yet to publish an app update.Btw, wouldn't you wanna check if the UniversalApiContract version 1 is present (instead of if version 2 is not present)? Because if version 3 is out, which is the one that'll come with the Anniversary Update I think, it'll also be false.Or do the UniversalApiContracts "stack" with each Windows version (until Microsoft decides to remove one)? As in, you have Windows 10 version 1511, so you have UniversalApiContract version 1 and 2, instead of just 2. And with the Anniversary Update, Windows will support UniversalApiContract version 1, 2 and 3 etc.. Is that how it works?
    • Anonymous
      June 20, 2016
      The comment has been removed
      • Anonymous
        June 20, 2016
        Yeah I've seen that noted in your post, about being able to test without store deployment on Redstone/Anniversary Update builds, that's great! I'll be testing on a version 1511 machine (and a machine running the latest Slow Ring build, currently 14366) and I'll let you know how it went. Thanks!
      • Anonymous
        June 22, 2016
        I've tested custom audio on both the 1511 and the Redstone machine and I can confirm it both works!
  • Anonymous
    August 28, 2016
    Oh, finally! Will custom sounds be also available on all other families, Xbox, HoloLens? I have quite robust framework in my app to handle mobile/dektop situation in terms of custom sounds. Not sure if it's safe to delete it all.
    • Anonymous
      August 28, 2016
      Frankly, I'm not sure about Xbox. HoloLens currently doesn't even support toast, so this is irrelevant there right now :PWe'll talk with the Xbox folks and hopefully write up a document stating what is and isn't supported on Xbox.