[Desktop Converter] MakeAppx.exe和Windows 10 Builds 14986.1001 / 14393.576 [英] [Desktop Converter]MakeAppx.exe and Windows 10 Builds 14986.1001 / 14393.576
问题描述
我关注的是谁：
我目前正在尝试将一些现有的.NET / C＃/ Windows窗体应用程序转换为通用Windows平台，以便在Windows应用商店中销售，并且在使用MakeAppx时遇到问题。 问题出现在
解析阶段的AppxManifest.xml文件中。
DesktopAppConverter目前只能进行转换过程，MakeAppx会抛出VisualElements / VisualElementsChoice节点错误C00CE014 - 清单验证错误。 我认为这是一个特定的错误
到最新版本的Windows 10 SDK和Windows 10本身，来自无数小时的在线研究。
但是，除了上面提到的Windows 10版本之外，我还在两台物理上不同的机器上安装了SDK版本26624,10586和14393，这两种版本都不允许MakeAppx解析AppxManifest.xml。
有人有什么建议吗？ 感谢您的时间。
- CCK
我的电路被炸了...
< blockquote>
你好CCK，
所以你试图使用DesktopAppConverter并试图按照这个文件手动转换你的包吗？
https://msdn.microsoft.com/en-us / windows / uwp / porting / desktop-to-uwp-manual-conversion
内部预览14965在我的机器上使用DesktopAppConverter时确实有问题但是我还没有在14986上进行了测试。但我认为最好将环境置于14393，因为这是一个稳定的版本。 然后我认为你的SDK
版本现在没问题，26624,10586和14393与目标10240,10586以及14393有关，在我看来它们都没问题。
因此问题可能与您的AppxManifest.xml文件或命令有关。但是我不知道你现在怎么写它们。所以我很难与大家分享这个建议。
因此我想为什么不首先按照桌面桥的常用过程进行操作？
1。通过参考在14393计算机上构建环境这里是
，请记得下载14393图片并通过选中"设置桌面应用转换器"来设置它。部分。
2。运行命令直接使用desktopappconverter来制作appx：
DesktopAppConverter.exe -Installer C：\Installer \ MyApp.exe
-InstallerArguments" ; / S" -Destination C：\Output \ MyApp -PackageName" MyApp"
-Publisher" CN =< publisher_name>" -Version 0.0.0.1 -MakeAppx -Verbose
3。如果您需要再次修改任何内容，请参阅
在这里编辑您的文件，然后再次makeappx。通过这种方式，您不需要设置太多可以节省一些时间并避免错误的事情。
祝你好运，
Barry
To Whom It My Concern:
I am currently attempting to convert some existing .NET/C#/Windows Forms applications to the Universal Windows Platform for sale in the Windows Store and am having trouble with MakeAppx. The problem arises in the parsing phase of the AppxManifest.xml file.
The DesktopAppConverter can only take the conversion process so far and MakeAppx is throwing the VisualElements / VisualElementsChoice node error C00CE014 - manifest validation error. I am under the impression this is a bug specific to the most recent build of the Windows 10 SDK and Windows 10, itself, from countless hours of online research.
However, in addition to the mentioned builds of Windows 10 being used, I have SDKs versions 26624, 10586 and 14393 installed on two physically different machines and neither build will allow MakeAppx to parse AppxManifest.xml.
Does anybody have any suggestions? Thank you for your time.
- CCK
My circuits are fried...
Hello CCK,
So you are trying to use DesktopAppConverter and you are trying to manually convert your package by follow this document?
https://msdn.microsoft.com/en-us/windows/uwp/porting/desktop-to-uwp-manual-conversion
The insider preview 14965 do has problem when using DesktopAppConverter from my machine however I haven't tested on 14986. But I think it's better that you put the environment in 14393 since this is now a stable version. Then I think your SDK version is alright right now, 26624, 10586 and 14393 is related to target 10240,10586 and also 14393, they are alright in my point of view.
So the problem may related to your AppxManifest.xml file or your command. However I have no idea about how you write them right now. So it's hard for me to share you the suggestion.
As a result I'm thinking that why not just follow the common process of desktop bridge first?
1. Build the environment on your 14393 machine by refer to here remember to download 14393 image and setup it by checking the "Set up the Desktop App Converter" part.
2. Run the command to use desktopappconverter directly to make the appx:
DesktopAppConverter.exe -Installer C:\Installer\MyApp.exe -InstallerArguments "/S" -Destination C:\Output\MyApp -PackageName "MyApp" -Publisher "CN=<publisher_name>" -Version 0.0.0.1 -MakeAppx -Verbose3. If you need to modify anything again just refer to here to edit your file and then makeappx again. In this way you don't need to setup so many things which may save you some time and avoid errors.
Best regards,
Barry
这篇关于[Desktop Converter] MakeAppx.exe和Windows 10 Builds 14986.1001 / 14393.576的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
