Add-AppxPackage -AppInstallerFile docs does not say that the package will be downloaded from the URL

[LevYas]

Hi!
I have a WPF app, which I package to MSIX and run functional end-to-end tests against a packaged and installed version. To install the package I used this command:

Add-AppxPackage -AppInstallerFile .\Bin\Packages\Installer.appinstaller

The appinstaller file contains a valid URL to the update server. I added some functionality and my tests started to fail. I noticed, that the previous version was used. I reproduced it on my local machine - I downloaded the package, verified that the application files are correct, and used the command above to install it. Instead of installing the app from the downloaded package, the command downloaded a previous version from the internet.

For now, I fixed this by changing command to
Add-AppxPackage ".\Bin\Packages\Installer_$Env:GitBuildVersionSimple.0_Test\Installer_$Env:GitBuildVersionSimple.0_x64.msixbundle"

(I use env variables from Nerdbank.GitVersioning)

I'm not sure whether it's the problem of docs or the Add-AppxPackage commandlet, but it would be nice to mention the current behavior difference in the docs.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: e5641ac1-f6b1-8ac1-51f3-21f367316168
• Version Independent ID: 6dcca508-5e35-5cb4-942b-22a20dbb1a4d
• Content: Add-AppxPackage (Appx)
• Content Source: docset/winserver2019-ps/appx/Add-AppxPackage.md
• Product: w10
• Technology: windows
• GitHub Login: @JasonGerend
• Microsoft Alias: jgerend

[officedocspr5]

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.

As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.

If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.

With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.

Here's what the new experience looks like.

Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.

First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful	Article was unhelpful

Finally, select Submit and you're done!