AppInstaller XML 问题 [英] AppInstaller XML Issue

问题描述

我正在尝试遵循 Microsoft 文档但我对我的应用程序安装程序失败的原因感到困惑:

I'm trying to follow the Microsoft documentation but I'm confused as to why my appinstaller is failing:

<?xml version="1.0" encoding="utf-8"?>
<AppInstaller xmlns="http://schemas.microsoft.com/appx/appinstaller/2018" Uri="https://xxxxxx.blob.core.windows.net/installer/Package.appinstaller" Version="1.0.0.0">
    <MainPackage Name="MyApp" Version="12.21.289.0" Publisher="CN=xxxxxx" ProcessorArchitecture="x64" Uri="https://xxxxxx.blob.core.windows.net/installer/MyApp.msix"/>
    <UpdateSettings> <OnLaunch HoursBetweenUpdateChecks="1" /> <AutomaticBackgroundTask/> </UpdateSettings>
</AppInstaller>

如果我运行 MSIX 文件，它会按原样安装.我一直在努力遵循这一点:如果我删除 UpdateSettings 属性，它只会导致另一个错误:"应用程序安装失败并显示错误消息:应用程序安装程序操作失败，错误代码为 0x80D05011.详细信息:未知错误 (0x80d05011)"

If I run the MSIX file, it installs as it should. I've been trying to follow this: https://docs.microsoft.com/en-us/windows/msix/desktop/azure-dev-ops I get this error: And if I remove the UpdateSettings attribute it will just cause another error: "App installation failed with error message: Appinstaller operation failed with error code 0x80D05011. Detail: Unknown error (0x80d05011)"

请帮忙.

推荐答案

虽然 Magikarp 的答案是正确的，但如果您阅读链接的完整线程，则有更好的解决方法.

While the answer from Magikarp is correct, if you read the full thread linked there is a better workaround.

开发人员:这个问题是由部分版本号超过一位引起的，比如 1.0.11.0，如果你让构建过程自动增加这些，就会很快发生.解决方法是升级到下一个版本 (1.1.0.0).

Developers: The issue is caused by part of the version number being more than one digit, like 1.0.11.0 which happens pretty quickly if you let the build process automatically increment these. The workaround is to roll over to the next version up (1.1.0.0) instead.

用户:任务管理器 ->服务 ->DoSvc ->重启这比重新启动系统更快更方便.

Users: Task Manager -> Services -> DoSvc -> Restart This is a bit quicker and more convenient than a system restart.

这个错误意味着只有 999 个有效的工作版本号(还没有测试 10.1.1 是否可行，但我知道 1.10.1 和 1.1.10 不可行)所以如果你打算快速迭代，你可能会想要重新考虑使用 Appinstaller 框架，至少在 Microsoft 提出修复方案之前.

This bug means that there are only 999 valid, working version numbers (have not tested if maybe 10.1.1 works but I know 1.10.1 and 1.1.10 don't) so if you are planning to iterate fast you might want to reconsider using Appinstaller framework at all, at least until Microsoft come up with a fix.

另请注意:服务的损坏状态是由此版本编号错误引起的，但一旦发生，重新启动是纠正它的唯一方法.

Also note: the broken state of the service is caused by this version numbering bug, but once it happens a restart is the only way to correct it.

这篇关于AppInstaller XML 问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！