Error using MSIX. In creating package, i got error. I will upload it here. Any help would be great!

%3CLINGO-SUB%20id%3D%22lingo-sub-1472879%22%20slang%3D%22en-US%22%3EError%20using%20MSIX.%20In%20creating%20package%2C%20i%20got%20error.%20I%20will%20upload%20it%20here.%20Any%20help%20would%20be%20great!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1472879%22%20slang%3D%22en-US%22%3E%3CP%3EHere%20is%20the%20error%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22package-title%20text-base%20ng-binding%22%3EMyPackageQuad_1.0.0.0_x64__wkffetrt8aq28.msix%3C%2FSPAN%3E%3CSPAN%20class%3D%22package-size%20ng-binding%22%3E8.3%20KB%3C%2FSPAN%3E%3C%2FP%3E%3CDIV%20class%3D%22row%22%3E%3CDIV%20class%3D%22col-xs-24%22%3E%3CDIV%3E%3CDIV%20class%3D%22alert%20alert-error%20reduced-string-length%20has-icon%22%3E%3CP%3EPackage%20acceptance%20validation%20error%3A%20The%20package%20MyPackageQuad_1.0.0.0_x64__wkffetrt8aq28.msix%20doesn't%20contain%20any%20Application%20elements%20in%20the%20app%20manifest%20file.%3C%2FP%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%3E%3CDIV%20class%3D%22alert%20alert-warning%20reduced-string-length%20has-icon%22%3E%3CP%3EPackage%20acceptance%20validation%20warning%3A%20The%20following%20restricted%20capabilities%20require%20approval%20before%20you%20can%20use%20them%20in%20your%20app%3A%20runFullTrust.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20much.%3C%2FP%3E%3CP%3ETony%3C%2FP%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1473967%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20using%20MSIX.%20In%20creating%20package%2C%20i%20got%20error.%20I%20will%20upload%20it%20here.%20Any%20help%20would%20be%20gre%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1473967%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F147865%22%20target%3D%22_blank%22%3E%40Bogdan%20Mitrache%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBogdan%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%20%26nbsp%3B%20Thanks%2C%20and%20ok.%20I%20will%20see%20what%20I%20can%20do%20about%20the%20%232%20item%20you%20stated%20here.%20%231%20is%20a%20bit%20confusing%20because%20I%20created%20an%20appxmanifest.xml%20file%20earlier%20and%20see%20elements%20in%20it%20that%20seem%20to%20be%20pretty%20straight%20forward%20as%20it%20pertains%20to%20the%20app.%20I%20thought%20this%20is%20what%20this%20error%20was%20pointing%20to.%20This%20seems%20to%20be%20the%20main%20problem%20right%20now.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThis%20is%20what%20I%20am%20confused%20about%3A%26nbsp%3B%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E1)%20%3C%2FSPAN%3E%3CSPAN%3EYou%20can%20see%20the%20entry%20points%20that%20were%20detected%20by%20the%20tool%20in%20the%20%22First%20launch%20tasks%22%20page.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EEntry%20point%20%3F%3F%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EIf%20you%20don't%20see%20your%20app's%20entry%20point%20here%2C%20you%20can%20add%20them%20with%20the%20%22Browse%22%20button.%26nbsp%3B%20Entry%20point%20%3F%3F%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20will%20look%20at%20what%20this%20%22Browse%22%20button%20is%20again%20and%20where.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1473298%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20using%20MSIX.%20In%20creating%20package%2C%20i%20got%20error.%20I%20will%20upload%20it%20here.%20Any%20help%20would%20be%20gre%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1473298%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F702965%22%20target%3D%22_blank%22%3E%40SBMSSOL%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1)%20Regarding%20the%20application%20element.%26nbsp%3B%3CSPAN%3EWhen%20the%20MSIX%20Packaging%20Tool%20generates%20a%20package%20it%20creates%20Application%20elements%20that%20represent%20the%20entry%20points%20to%20your%20application%20and%20each%20has%20an%20App%20ID.%20You%20can%20see%20the%20entry%20points%20that%20were%20detected%20by%20the%20tool%20in%20the%20%22First%20launch%20tasks%22%20page.%20If%20you%20don't%20see%20your%20app's%20entry%20point%20here%2C%20you%20can%20add%20them%20with%20the%20%22Browse%22%20button.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2)%20This%20capability%20%22runFullTrust%22%20is%20mandatory%20for%20any%20Win32%20application%20packaged%20as%20MSIX.%20When%20you%20publish%20the%20app%20to%20the%20store%20you%20simply%20mention%20in%20the%20comments%20are%20this%20is%20a%20Win32%20converted%20app%20and%20the%20submission%20team%20should%20accept%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Here is the error:

 

MyPackageQuad_1.0.0.0_x64__wkffetrt8aq28.msix8.3 KB

Package acceptance validation error: The package MyPackageQuad_1.0.0.0_x64__wkffetrt8aq28.msix doesn't contain any Application elements in the app manifest file.

Package acceptance validation warning: The following restricted capabilities require approval before you can use them in your app: runFullTrust.

 

Thank you much.

Tony

6 Replies

Hi @SBMSSOL 

 

1) Regarding the application element. When the MSIX Packaging Tool generates a package it creates Application elements that represent the entry points to your application and each has an App ID. You can see the entry points that were detected by the tool in the "First launch tasks" page. If you don't see your app's entry point here, you can add them with the "Browse" button.

 

2) This capability "runFullTrust" is mandatory for any Win32 application packaged as MSIX. When you publish the app to the store you simply mention in the comments are this is a Win32 converted app and the submission team should accept it.

@Bogdan Mitrache 

 

Bogdan,

 

    Thanks, and ok. I will see what I can do about the #2 item you stated here. #1 is a bit confusing because I created an appxmanifest.xml file earlier and see elements in it that seem to be pretty straight forward as it pertains to the app. I thought this is what this error was pointing to. This seems to be the main problem right now.

 

This is what I am confused about:  

 

1) You can see the entry points that were detected by the tool in the "First launch tasks" page. 

Entry point ???

 

If you don't see your app's entry point here, you can add them with the "Browse" button.  Entry point ???

 

I will look at what this "Browse" button is again and where.

Hi @SBMSSOL 

 

Sorry, since you didn't mention I supposed you used the MSIX Packaging Tool to create the package. That is the case for more questions around this community.

From I see you don't? How did you create the package? From Visual Studio?

 

Can you extract  (just unzip with something like 7-zip) and share as an attachment the manifest from the package that gave you the error?

 

As a clarification - an "entry point" is how the community refers to an executable that is marked as as shortcut for the app. i..e Since the app runs inside the MSIX container this exe is the "entry point" in the package container.

@Bogdan Mitrache 

 

This is what I am using. MSIX Package app screen. I tried to add this to my VS but without success. I am using VS Community. I have now gotten this other message doing what you said with the browse button. ??? Thanks for your assistance.

Ooo, it looks like either the MSIX Packaging Tool has an issue or the package you're trying to convert is more complicated.

 

Have you tried the free Express edition from Advanced Installer? It has similar conversion capabilities, but with some major enhancements for certain areas.

 

Or, can you share a download link for the package you are trying to convert so we can try it too?

 

 

As a separate note. Since you are planning to go to the Store with this package I can only assume you are the owner of this app. In this case, converting the existing setup package to MSIX is not the recommended method.  You can simply create your package from Visual Studio, either using the free extension from Advanced Installer or the one from Microsoft.

 

The process where you convert an existing installer to MSIX format is recommended mostly for IT professionals which usually are not the owner of the app (i.e. without access to its source code).

 

@Bogdan Mitrache 

 

Bogdan,

 

    Ok, thank you, I will try this. This seems to be able to be solved simply enough by me, just that Microsoft has a tendency to make things harder than they should be. Thanks for this information, and yes, I am the owner. I tried to download this in VS 2019 Community but keep getting an error about can't install WinSDK_10.0.18362.  ??? This is when I try to add the Windows application Package to my VS 2019 Community Edition. This is why I tried using the MSIX Tool separately. I seem to have made much progress in doing this. Also, My app is not complex, just a Quadratic Equation formula software to calculate the Quadratic Equation. No database attached to it at all. I may send and share my package with you when I get a chance. I may be doing something minor wrong here, just don't know what yet. But it is fun to solve these problems.