Blog post "Building and Deploying a Local Appx Package" at http://blog.marcocantu.com/blog/2016-november-building-deploying-appx.html

-
Blog post "Building and Deploying a Local Appx Package" at http://blog.marcocantu.com/blog/2016-november-building-deploying-appx.html
http://blog.marcocantu.com/blog/2016-november-building-deploying-appx.html

Comments

  1. Eden WUNovember 26, 2016 at 3:05 PM

    I have MS Developer account.

    About "The IDE also support deployment for Windows Store, using slightly different steps"

    Could you tell me how to steps? Please!

    Thanks!

    ReplyDelete
  2. Marco CantùNovember 27, 2016 at 2:44 AM

    Eden WU To create a store-ready APPX package, go the Provisioning page of the project options and fill in the bottom part of the pane, rather than the top part. The information to be added there (app is, user info) is provided by Microsoft after you create an app on their store (with a developer account)

    ReplyDelete
  3. Eden WUNovember 27, 2016 at 2:52 AM

    Marco Cantù
    I have set Strore option in Options->Provisioning, and write Package Name, Package Display... in the App Identity GroupBox.

    After how to do it?

    ReplyDelete
  4. Marco CantùNovember 27, 2016 at 2:56 AM

    After you filled those boxes, just do a deploy, and you'll get an unsigned APPX with the proper manifest data.

    ReplyDelete
  5. Eden WUNovember 27, 2016 at 3:00 AM

    Marco Cantù
    So, I can direct upload appx what using depley from Store option compile?

    Great!
    I will try it, thank you Marco!
    Thank you again!

    ReplyDelete
  6. Eden WUNovember 27, 2016 at 4:29 AM

    Marco Cantù I get the error message when upload appx package to store.

    "Package acceptance validation error: You did not specify the following namespace permissions in the Appx manifest file for the package EdenFirstApp.appx: http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities

    Package acceptance validation error: Your developer account does not have permission to submit apps converted with the Desktop Bridge at this time. Https://aka.ms/desktopbridgeforwindowsstore"

    ReplyDelete
  7. Marco CantùNovember 27, 2016 at 7:02 AM

    Eden WU Did you read my blog posts on this subject (http://blog.marcocantu.com/blog/2016-november-delphi-appx-win10-store.html, second last paragraph has the links). This is the default configuration by Microsoft. The Windows Desktop Bridge support gets enabled by Microsoft on specific developer accounts on request. You need to have an application to publish, provide information (and a web page) covering it, and submit for approval after the account has been enabled.

    It not a great process, but they seem fairly fast. And you need to sign a specific (and far from ideal) agreement with Microsoft, giving guarantees on the application behavior (or lack of mis-behavior).

    ReplyDelete
  8. Eden WUNovember 27, 2016 at 10:06 PM

    Marco Cantù
    The original real reason is "runFullTrust"...

    blogs.msdn.microsoft.com - Take Action: Convert your Windows Desktop App and bring it to Windows 10 Store

    ReplyDelete
  9. Marco CantùNovember 27, 2016 at 11:26 PM

    Eden WU Correct, runFullTrust is part of the Windows Desktop Bridge "extra allowance", requires permission from Microsoft. This is how the bridge works and there is nothing we can do at our end to change that.

    ReplyDelete

Post a Comment