Replies: 3 comments 1 reply
-
I'm having the same problem... it doesn't help that there's absolutely no documentation on the various appx parameters for msbuild :-\ |
Beta Was this translation helpful? Give feedback.
0 replies
-
@Marv51 did you end up trying the |
Beta Was this translation helpful? Give feedback.
1 reply
-
A solution was posted here - cross-referencing it here so it's easier to find: MicrosoftDocs/msix-docs#326 (comment) <PropertyGroup>
<CreatePackageMakeAppxParameters>/pb "C:/[full-path-worked-for-me]/certificate-migration-2022-pb.txt"</CreatePackageMakeAppxParameters>
<CreateResourcePackageMakeAppxParameters>/pb "C:\[full-path-worked-for-me]\certificate-migration-2022-pb.txt"</CreateResourcePackageMakeAppxParameters>
<AppxPackageSigningEnabled>false</AppxPackageSigningEnabled>
</PropertyGroup> |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Unfortunately our new code signing certificate has some changes compared to our old one. So to keep the same identity I am following this help page on: MSIX persistent identity .
The page manually calls makeappx with a
/pb
or/publisherBridging
parameter.Now I am using WinAppSDK and WinUI 3 so my packaging is done with the packaging project (.wapproj).
Can I pass an msbuild parameter to set that makeappx parameter somehow?
If not, do you have any instructions available how to manually create an msixbundle from my WinAppSDK/WinUI 3 project?
Beta Was this translation helpful? Give feedback.
All reactions