User Profile
RahulAdb
Copper Contributor
Joined 7 years ago
User Widgets
Recent Discussions
How to specify registry entries inside the package created by MakeAppx.exe
We are using MakeAppx.exe (manual packaging) to author MSIX package. Our earlier installer (scripted) used to create registry entries under the hives HKEY_CLASSES_ROOT (file association, CLSIDs, preview HKEY_LOCAL_MACHINE (The list is attached). Please guide how we can configure these with the manual packaging route. Is there any way to author the registry.dat.943Views1like1CommentRe: Manually creating MSIX packages using Packaging Layout
This is confusing. In another thread it was specified that there is no need to differentiate between APPX and MSIX. APPX is a subset of MSIX. https://techcommunity.microsoft.com/t5/MSIX-Packaging-and-Tools/Differentiating-between-appx-and-msix-packages/m-p/356092#M336 Also in another thread it was mentioned that MakeAppx.exe will automatically generate MSIX or APPX based on the package content. https://techcommunity.microsoft.com/t5/MSIX-Packaging-and-Tools/How-to-specify-package-type-msix-or-appx-using-manual-packaging/m-p/356070#M333 What new feature is being talked about here?1.8KViews0likes2CommentsRe: Suggested communication way between MSIX/win32 apps
- We have the code, however not all apps can migrate to new packaging together. - Additionally before changing the code, we are looking to just repackage the existing binaries. In future when we migrate and utilize full power of Windows 10 and MSIX we can look to change code.2.9KViews0likes0CommentsRe: Suggested communication way between MSIX/win32 apps
What is meant by "packaged together". Do you mean inside a single MSIX package? If we mark A & B as full trust applications, can they then communicate with each other and C as well over standard IPC techniques like named pipes.2.9KViews0likes2CommentsRe: How to specify package type (.msix or .appx) using manual packaging tool (Makeappx.exe)
We use the following command to generate the package. MakeAppx pack /m "MyApp\AppxManifest.xml" /f MyMapping.txt /p AppPackage.msix What would be the difference in the makeup of the app that will result in the difference between a .msix and .appx.1.8KViews0likes2CommentsHow to specify package type (.msix or .appx) using manual packaging tool (Makeappx.exe)
The MSDN document for manual packaging specifies that MakeAppx.exe can be used to generate both MSIX and APPX packages. However it is not clear as which option can be used to guide the tool to generate these different package types. Is there any such option? We tried this by changing the extension of the output package specified in the command line (/p abc.appx or /p abc.msix). There seemed to be no difference in the content of the generated packages.1.9KViews0likes5CommentsRe: failed to process request 8bad0031 with Win7Msix
Thanks for quick response John, Yes, the appx was signed using a self signed certificate. I will try it by using a derived certificate. The sample attached in the GIT repo do not work as well? samples: https://github.com/Microsoft/msix-packaging/tree/master/preview/Win7Msix/Tests On Windows 7, What will be the difference between the apps installed using MSIX or MSI route. Will the security/container benefits of MSIX still apply?1.2KViews0likes1Commentfailed to process request 8bad0031 with Win7Msix
Installing an .appx package with Win7MSIXInstaller.exe results in error : failed to process request 8bad0031 Command line used: Win7MSIXInstaller.exe -AddPackage abc.appx OS - Windows 7 SP1 (6.1 Build 7601) The appx package was created using MakeAppx.exe Issue is reproduced by using both the pre-compiled and self-compiled binary. Pre-compiled binary: https://github.com/Microsoft/msix-packaging/tree/master/preview/Win7Msix/Binaries1.2KViews0likes3Comments
Groups
Recent Blog Articles
No content to show