none
Submitting a headless app to the Universal Store

    Question

  • I'm working on publishing a headless app to the app store for a commercial application.  

    Following these instructions (https://developer.microsoft.com/en-us/windows/iot/docs/store), I created a Blank App (Universal Windows), compile it and add the EXE to the headless app project.

    When compiling for Release, I get the message "An executable image named '<APPNAME>.winmd could not be found in <C:\Projects\<APPNAME>\obj\x86\Release\ilc\in".

    • The message does not occur when the EXE is removed from the project
    • The message does not occur when you don't "Compile with .NET Native tool chain", which is a requirement for store submission
    • I am able to "Create App Packages" for the Store without the headed app, but it fails the subsequent assessment on my machine because it doesn't have a headed app to launch

    Has anyone got this process to work?  Am I missing a step in the process?

    Thursday, February 9, 2017 4:46 PM

Answers

  • I ended up opening a support incident.  The workaround provided was simple:  Add the EXE to a folder in the solution and it will build.  

    In the Package.appxmanifest, ensure you specify the folder in the Application node:

        <Application Id="App" Executable="EXE\DummyApp.exe" EntryPoint="DummyApp.App">

    In my case, the blank UWP app is in a folder named "EXE".  I also specified "Copy to Output Directory" as "Copy Always"

    Friday, February 17, 2017 9:03 PM

All replies

  • Hi Grit-Grumble,

    A quick search https://social.msdn.microsoft.com/Forums/en-US/home?forum=WindowsIoT&sort=relevancedesc&brandIgnore=True&searchTerm=https%3A%2F%2Fdeveloper.microsoft.com%2Fen-us%2Fwindows%2Fiot%2Fdocs%2Fstore shows all other postings related to the instructions to use the store with IoT Core.

    Also, there are two posts with a similar error to yours if you search https://social.msdn.microsoft.com/Forums/en-US/home?forum=WindowsIoT&sort=relevancedesc&brandIgnore=True&searchTerm=winmd

    The other threads suspect a tooling issue so you might want to submit this issue to VS or the store.

    Sincerely,

    IoTGirl

    Friday, February 10, 2017 12:00 AM
    Moderator
  • I'm working on publishing a headless app to the app store for a commercial application.  

    Following these instructions (https://developer.microsoft.com/en-us/windows/iot/docs/store), I created a Blank App (Universal Windows), compile it and add the EXE to the headless app project.

    When compiling for Release, I get the message "An executable image named '<APPNAME>.winmd could not be found in <C:\Projects\<APPNAME>\obj\x86\Release\ilc\in".

    • The message does not occur when the EXE is removed from the project
    • The message does not occur when you don't "Compile with .NET Native tool chain", which is a requirement for store submission
    • I am able to "Create App Packages" for the Store without the headed app, but it fails the subsequent assessment on my machine because it doesn't have a headed app to launch

    Are there updated instructions for this process available?  

    • Merged by Mattew Wu Tuesday, February 14, 2017 5:43 AM duplicated
    Monday, February 13, 2017 9:31 PM
  • We were able to verify two items at this point:

    • Replacing Microsoft.NetNative.Targets does not affect the behavior
    • We see the same thing on any tested dev station (VS 2015 Update 3) and in the current VS 2017 RC

    I posted in the Submitting and Publishing Apps forum, but it got merged back here.  Is there something else different I was supposed to do when you stated: "submit this issue to VS or the store"

    Tuesday, February 14, 2017 10:05 PM
  • I ended up opening a support incident.  The workaround provided was simple:  Add the EXE to a folder in the solution and it will build.  

    In the Package.appxmanifest, ensure you specify the folder in the Application node:

        <Application Id="App" Executable="EXE\DummyApp.exe" EntryPoint="DummyApp.App">

    In my case, the blank UWP app is in a folder named "EXE".  I also specified "Copy to Output Directory" as "Copy Always"

    Friday, February 17, 2017 9:03 PM
  • Thanks for the follow up!
    Friday, February 17, 2017 11:37 PM
    Moderator