Flor Chacón

There is no way to specify a client ID or scope. App Installer uses its own client ID and sets the scope depending on whether the resource is on SharePoint...

I'm not sure I'm understanding what you are trying to accomplish. Are you trying to get Visual Studio to publish you MSIX package or .appinstaller file to a location that...

The `msixauth` parameter is not something you need to worry about as part of the MSIX package creation. If you need authentication to access the place you're publishing the package...

I'm able to reproduce this issue on my computer. My gut feeling is that it is a bug on the App Installer at the intersection of installing .appinstaller files and...

> just the links to the index.html Not sure what links you mean here But yes, you should not need to change anything on the .appinstaller or .msixbundle files for...

Yes, this needs an update to App Installer. Unfortunately, I don't have an ETA of when that will be available.

I've been looking into this recently. I think there is a way to make it work if you hold it just right. Let's say your .appinstaller file is going to...

The AppInstaller and MainBundle elements look right to me. For the dependencies, I think you'd also need to add `?msixauth=aad` at the end, but I'd suggest trying to get it...

You have to host the files in either SharePoint/OneDrive or Azure Blob Storage and use URIs to that. These are the only two places that currently work for msixauth. App...

TL;DR: Use "S" instead of "ST" The tooling uses [`CertNameToStr`](https://learn.microsoft.com/windows/win32/api/wincrypt/nf-wincrypt-certnametostra) to compute the expected publisher string from the certificate. It has some quirks mentioned in the [Remarks](https://learn.microsoft.com/windows/win32/api/wincrypt/nf-wincrypt-certnametostra#remarks), for example it...