User Profile
Chacon
MicrosoftJoined 6 years ago
User Widgets
Recent Discussions
Re: MSIX packing error on Windows11
Ley This is the relevant line: > MakeAppx : error: You can't add both "%UserProfile%\AppData\Local\Packages\Microsoft.MSIXPackagingTool_8wekyb3d8bbwe\LocalState\DiagOutputDir\Logs_3\iy5ing5x.xx5.Manifest" and "C:\Program Files\Microsoft Office\AppXManifest.xml" to the output file as "AppXManifest.xml" Looks like you want to include an existing AppXManifest.xml. The MSIX Packaging Tool attempts to generate one automatically from the changes detected during installation. The error comes because the package can only have one manifest file, but there are two (one auto-generated by the tool, and the one under C:\Program Files\Microsoft Office). If the file "C:\Program Files\Microsoft Office\AppXManifest.xml" something you are creating, you can try not including it and then editing the generated manifest after the fact.2.5KViews0likes2CommentsRe: MakeAppx with publisher bridge - error ID=0x80080218, Error=317
Error 0x80080218 does signal that the publisher bridging file is not set up correctly. It's hard to know exactly why without more details. One possible reason is if you are using the "new" publisher name in the manifest instead of the "old" one. The artifact will let you sign using a cert with the "new" name, but you still have to use the "old" name in the manifest.1.9KViews1like1CommentRe: How to properly escape a comma in makeappx.exe package process?
jackd5O I believe you can include the comma by quoting the field. So it would be 'CN="MSFT, INC", O="MSFT, INC", C=US'. To include those inner quotes in the manifest XML, you would need to escape them as " so it would ultimately look like Publisher="CN="MSFT, INC", O="MSFT, INC", C=US". Note that the regex says you cannot use special characters, unless you quote them: ([^ ,+="<>#;]+|".*") means that you can write something without any of those characters, or you can surround the full thing with quotes.2.1KViews0likes1CommentRe: Questions about MMPT remote packaging
Yes, the remote machine needs to have the driver. If it is not already installed, Windows Update needs to be enabled to install it, but only the first time. You could also do an offline installation of the driver beforehand. If the MSIX Packaging Tool is already installed on the remote machine, it may have already installed the driver and the remote server would not need to install it.1.5KViews0likes1CommentRe: MSIX Packaging Tool usage issues
Hi wangli2230 Are you the developer of the application you are trying to package? If that is the case, the MSIX Packaging Tool may not be the right tool to use. We recommend you create your package directly from source code, using a Windows Application Packaging Project or MakeAppx.exe. The MSIX Packaging Tool is intended to package applications using their installers, not the applications themselves, and is intended for scenarios where you do not have access to the source code. It will execute the installer and see what files it creates. The applications listed in the "First launch tasks" step will be those whose executable files (.exe) were created by the installer (and have a shortcut). I believe your application was not listed because you used your app's .exe instead of an installer for it. The "App packager error" that you see is because the tool detected an app manifest AppxManifest.xml but the tool auto generates one from the data it collects, and that causes a conflict. Since you already have an AppxManifest.xml, you probably can use it to create your package without the MSIX Packaging Tool.1.6KViews1like0CommentsRe: Create MSIX Package in Release Pipeline!
Hi s_salaria The AppxManifest.xml should be in the root of the directory you are packaging. So you need to either move it to the BRMS_Packaging_MSIX\Shell\ directory or point the task to the BRMS_Packaging_MSIX\ directory. (Which probably means that the task doesn't actually need to ask for the path to the manifest, or that if it does it should be using it even if it's not at the root.) In your manifest file I noticed that there is a reference to a Shell\*.exe file and several Images\*.png files. These files must exist relative to the input directory, so you will want the directory you pass to the task to look something like this: \ AppxManifest.xml Shell\ BRMSv2.exe ... Images\ StoreLogo.png ...4.3KViews0likes1CommentRe: Create MSIX Package in Release Pipeline!
s_salaria , Are you trying to create an MSIX package or an MSIX bundle? Sorry, I just assumed you wanted a single package before. You can see a bit more about bundles here: Bundling MSIX packages - MSIX | Microsoft Docs If you are trying to create a single package, you need to un-select the option "Generate MSIX Bundle". If you select that option, the task will expect a directory containing the multiple .msix packages from which it will create an .msixbundle. If you don't select it, it will expect a directory with binaries, assets and an AppxManifest.xml to create an .msix. The error comes from selecting to produce an MSIX bundle, but using a directory with loose files.4.2KViews0likes3CommentsRe: Create MSIX Package in Release Pipeline!
In the "MSIX build and package" task, un-select the option "Build solution with MSBuild". Then instead of pointing it to the .sln you will have to point it to the directory containing the contents of the package (like dlls, config and assets) which you already built. This directory also needs to have an AppxManifest.xml. You could create this by hand, but I believe the VSBuild task should already be creating it for you from the Package.appxmanifest file.4.3KViews0likes5CommentsRe: Create MSIX Package in Release Pipeline!
Hi s_salaria, I believe the app.config file is only copied by the build process to a path similar to <output>.dll.config. In that case, you can have your build pipeline publish the multiple app.config files for each environment, then in the release pipeline copy the appropriate file to the right location before creating the MSIX. This wouldn't apply if the build process modifies or uses the app.config file in any way (which is not the case AFAIK), because then you would have to set which one to use at build time.4.3KViews0likes7CommentsRe: Create MSIX Package in Release Pipeline!
Hi s_salaria , How do specify the env specific configurations for your packages? E.g. whether you modify the manifests, or add a flag when compiling, or something else. Knowing that could help us find a way to do what you need. If you use the MSIXPackaging task, you will want to point either To the .sln file and .appxmanifest in your sources directory $(Build.SourcesDirectory), to compile into DLLs/EXEs and then create an MSIX (so you skip the VSBuild step); or To a directory with your already compiled DLLs/EXEs and an AppxManifest.xml, to create the MSIX from that without compiling. This could be in your $(Build.BinariesDirectory) if you pointed the VSBuild step to place the files there. I know that doesn't answer your question, but hopefully helps to move in the right direction.4.3KViews0likes10CommentsRe: MSIX Packageing Tool / signtool certificate issues
Hi Mo_Velayati If the certificate subject is SERIALNUMBER=123456-78, C=US, ST=STATE, L=CITY, STREET=Address more address, O=A Company, INC., CN=A Company, INC. then this Publisher should work: Publisher="SERIALNUMBER=123456-78, C=US, S=STATE, L=CITY, STREET=Address more address, O="A Company, INC.", CN="A Company, INC."" I just tested signing a package with that exact publisher and a self signed certificate. Things to note: The order of the fields is the exact same (without CN at the start) ST becomes S The O and CN fields are quoted because they include commas If that doesn't work, you can try using signtool.exe for finding the error (even if you end up using AzureSignTool after figuring it out). There are two things that you can do with signtool for debugging: Add the /debug flag. That may help if the issue is with the certificate (e.g. not enabled for signing or expired). Set the APPXSIP_LOG environment variable to a value from 1 to 3 depending on how much logging you want. This would tell you if there is a mismatch between the publisher and the certificate subject, and what is the correct value. For example ERROR: [Appx::Packaging::SipFunctionHelper::VerifyManifestPublisherName] failed because signing certificate subject name (SERIALNUMBER=... <cert's subject>) does not match package manifest publisher (CN=... <package's publisher>) You may be able to do something similar with AzureSignTool but I'm not familiar with it. To do this you would need to have the certificate available in your machine, not in Azure Key Vault (only to debug). You can download your certificate or create a self signed certificate with the same subject. See: Create a certificate for package signing - MSIX | Microsoft Docs.1.7KViews0likes0CommentsRe: MSIX Packaging tool AV detection
Hi JeffAre Thank you for reporting this. The Microsoft Defender team determined this to be a false positive and has updated their security intelligence. The changes will reflect in latest security intelligence version 1.329.2889.0 or above. This security intelligence update will be available to users who subscribe to the automatic security intelligence update mechanism, as well as users who choose to manually update security intelligence update. The latest security intelligence update is available for download here: https://www.microsoft.com/en-us/wdsi/definitions1.3KViews0likes0CommentsRe: Microsoft MSIX Packaging Tool and COM Capture issues leading to incorrect manifests
Thank you for alerting us of this TIMOTHY_MANGAN , As I understand this is the same issue you reported earlier in MSIX Packaging Tool failure due to non-unique Com:ProxyStub - Microsoft Tech Community, or am I missing something? This is in our backlog and we will fix it for future releases of the tool. In the meantime, I managed to reproduce the issue and I will let you know if I find any possible workaround to make the tool do the right thing without manually editing the manifest.621Views0likes0CommentsRe: Getting the MSIX package tool to install the needed tool drivers to work
Hi rkeil1910 Does any of the documentation at https://aka.ms/driverconsiderations help you? The logs for the tool could help narrow down the issue. The error prompt should contain a link to the log folder, and in there should be a Log.txt file. It should contain the exit code and any output from dism.exe when it failed to install the driver. If you are building this tool yourself, we recommend you build the package directly instead of converting it with the MSIX Packaging Tool from another installer, as it gives you better control of what will be in the package. For example, you can use a Windows Application Packaging Project in Visual Studio.882Views0likes0CommentsRe: MSIX Packaging Tool failure due to protocol handler
TIMOTHY_MANGAN I believe this is related to what was described in WinSCP fails both manually and automated on W10 20H2 with latest tool build - Microsoft Tech Community As you said the tool used the uap10 prefix instead of uap3 unnecesarily. Then, it created an <uap10:Protocol> element that contained a <uap:DisplayName> instead of <uap10:DisplayName> causing MakeAppx to reject it. Both issues should be fixed in the latest Insider build of the tool (1.2020.1219.0). I.e., it should use uap3:Protocol in this case and uap10 only when actually needed (e.g. length >= 40), and when it does, the element has the appropriate children.984Views0likes1CommentRe: Deployment by Appinstaller cause URI handling popup without the app link
vshmelev This should work correctly with the Windows 10 October 2020 update. On previous builds there was an issue with AppUriHandler that caused it not to work when installing with an App Installer file, exactly as you described.2.1KViews0likes1CommentRe: MSIX COM PROGID CLSID is invalid
xenappblog From what I see, the MSIX Packaging Tool is not detecting the COM registrations for this app correctly. Then, when you execute it it fails because the package is missing the needed COM registrations. I tried converting the app and the tool seems to be having issues converting the registrations for InprocServer and registrations under the WOW6432Node key on x64. I'm not sure if there is a way to tweak the registrations to make the tool detect them correctly. Thank you for reporting this. We will look into fixing it for future releases of the tool.1.7KViews1like0CommentsRe: WinSCP fails both manually and automated on W10 20H2 with latest tool build
Hi xenappblog I tried converting WinSCP and I believe the error you are seeing is due to an invalid protocol association. The MSIX Packaging Tool creates this protocol association: <uap10:Protocol Name="s3" Parameters="/Unsafe "%1""> <uap:DisplayName>s3</uap:DisplayName> <uap:Logo>Assets\dav.png</uap:Logo> </uap10:Protocol> It should be using uap3:Protocol, not uap10:Protocol. There are other protocol associations, but only this one seems to be invalid. To fix this you can edit the manifest file manually using the Package Editor. To do this, in the "Create new package" page of the tool, click "Package editor" instead of "Create" and then look for the "Open file" button at the bottom of the page.1.9KViews0likes2CommentsRe: Deployment by Appinstaller cause URI handling popup without the app link
Hi vshmelev , I just tried installing your app and the web-to-app linking worked for me in both cases (with the .msix and with the .appinstaller), so it seems like your package and App Installer file are okay. You can file feedback through Feedback Hub using the category "Install and Update" \ "App installation issues". When filing the item, recreate the problem so that it will collect relevant traces and attach them. After you do, you can send me a link to the item so we can investigate it.2.3KViews0likes3CommentsRe: MSIX Packaging Tool and Registry User.Dat and UserClasses.Dat files
TIMOTHY_MANGAN Thank you for reporting this. In the future, the MSIX Packaging Tool will ensure User.dat gets created even if there are no changes to HKCU\Software\Classes. In the meantime, as you said, you can create an extra registry key under HKCU\Software\Classes to ensure User.dat is created.3.4KViews0likes0Comments
Recent Blog Articles
No content to show