This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(236.8, 40%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESP%3C/text%3E%3C/svg%3E)
Hello;
With Visual Studio 2019 Version 16.8.4, a WPF C++ Managed project, which I can successfully build, it fails to publish with error:
error : PRI180: 0x80070057 - Target ARM64\Release\PackageUploadLayout does not exist
error : PRI193: 0x80070057 - Please provide a valid Project Root
It happens on a empty project as well. It seems to be related to C++ Managed.
The project targets SDK 10.0.19041.0, no other dependencies
Any suggestion ?
Locked Question. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(179.20000000000002, 21%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYG%3C/text%3E%3C/svg%3E)
@Stéphane Denis Could you please tell me if you are packaging your WPF project as a UWP project by using Desktop Bridge?
No I'm packaging from Visual Studio, using the Publish, Create App Packages, selected 'Microsoft Store as .XXXX'. then Select and configure padckages, Architecture : x86, x64, ARM, ARM64, include public symbols, Generate artifacts to validate the app, then create.
After those steps, the build successfully complete for the 4 archs, and when it cames to packaging, cames the error
Unchecking ARM64 works (generating ARM).
The app was already published on Windows Store, only changes was to add the ARM64 arch.
@Stéphane Denis It is suggested to use Desktop Bridge to publish your WPF app to Microsoft Store as what I said in previous comment.
The key point is to use the Windows Application Packaging Project project to generate a package for your desktop app. For the detailed steps about how to package your WPF app, you could refer to the document. Then you need to publish the Windows Application Packaging Project project to the Microsoft Store referring to the document.
Hello, this is not a Desktop App, but an UWP App. I don't need to repackaging. Also I've checked the page, and already following the instructions. Note that in the link, the ARM64 is not checked.
https://learn.microsoft.com/en-us/windows/msix/package/images/packaging-screen5.jpg
So it means that ARM64 is not supported in UWP ?
@Stéphane Denis You said that your app is a WPF C++ Managed project in the description of the case, but you also said your app is a UWP app in a reply. I'm confused that what the type of your app is.
ARM64 is supported in UWP app. You could refer to the document which indicates Universal Windows Platform (UWP) apps can be configured to run on the following architectures: x86, x64, ARM, ARM64. And you need to select the ARM64 architecture just like select the x86, x64 and ARM architecture to allow a UWP app to run on ARM64 devices. For more information about targeting the ARM64 platform, you could refer to the document.
This is my Case: Manifest references file 'Microsoft.Graphics.Canvas.dll' which is not part of the payload. It has cost me two weeks, and I still can't release this APP.
I have compared build log of success one and failed one, I found "Target ARM64\Release\PackageUploadLayout does not exist" maybe caused by .NET Native compilation failed to started for some reason.
If you have any progress or tips, please let me know. Thanks!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(38.4, 82%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
I got exactly same error, after ARM64 option checked, publish error.
on VS2109 v16.8.5
Severity Code Description Project File Line Suppression State
Error PRI180: 0x80070057 - Target ARM64\Release\PackageUploadLayout does not exist
Severity Code Description Project File Line Suppression State
Error PRI193: 0x80070057 - Please provide a valid Project Root
I also got this error:
_GenerateAppxPackageRecipeFile:
MyApp.UWP -> D:\MyApp\MyApp.UWP\bin\x86\Release\MyApp.UWP.build.appxrecipe
_CreatePackageLayout:
Directory "obj\x86\Release\PackageLayout\" doesn't exist. Skipping.
MyApp.UWP -> obj\x86\Release\PackageLayout\
_SplitResourcesPri:
C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\x64\MakePri.exe New -ProjectRoot obj\x86\Release\PackageLayout\ -ConfigXml obj\x86\Release\split.priconfig.xml -OutputFile obj\x86\Release\split.pri -IndexName 3B3C62F3.5494505C4A71E -MappingFile AppX -Verbose -Overwrite
GENERATEPROJECTPRIFILE : error : PRI180: 0x80070057 - Target obj\x86\Release\PackageLayout does not exist
GENERATEPROJECTPRIFILE : error : PRI193: 0x80070057 - Please provide a valid Project Root
Sorry to bump this old thread, still have issue Microsoft Visual Studio Community 2022 (64-bit) - Current Version 17.7.3
GENERATEPROJECTPRIFILE : error : PRI180: 0x80070057 - Target ARM64\Release\PackageUploadLayout does not exist
Still no real support for ARM64/C++ in 2023 ?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 20%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAG%3C/text%3E%3C/svg%3E)
Acabo de tener este problema para ARM64, para solucionarlo deben modificar su archivo .vcxproj, deben buscar la sección:
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|ARM64'" Label="Configuration">
Aquí encontraran la propiedad:
<UseDotNetNativeToolchain>true</UseDotNetNativeToolchain>
Cambian true por false, esto funcionó para mí, aunque no creo que sea la forma correcta de solucionar este problema, ya que si se está usando código administrado, este no será compilado a nativo con esta opción desactivada, esto puede empeorar el rendimiento para dicha plataforma, acabo de crear otro proyecto nuevo y en este funciona el empaquetado para ARM64 en Release con UseDotNetNativeToolchain=true, así que esto confirma que el error se debe a alguna modificación que le hice al archivo de proyecto.