├── .gitattributes ├── .github └── fabricbot.json ├── .gitignore ├── .openpublishing.publish.config.json ├── .openpublishing.redirection.json ├── LICENSE ├── LICENSE-CODE ├── README.md ├── SECURITY.md ├── ThirdPartyNotices └── msix-src ├── app-installer ├── How-to-create-custom-app-installer-ux.md ├── app-installer-api-issues.md ├── app-installer-authentication-manager--overview.md ├── app-installer-documentation.md ├── app-installer-file-overview.md ├── app-installer-root.md ├── app-installer-security-features.md ├── app-installer-ui-dialog.md ├── auto-update-and-repair--overview.md ├── create-appinstallerfile-vs.md ├── how-to-create-appinstaller-file.md ├── how-to-embed-an-appinstaller-file.md ├── images │ ├── App-Installer-File-Update.png │ ├── Install-asp.png │ ├── add-package.png │ ├── app-installer-smart-screen.png │ ├── app-installer-ui-dialog-update.png │ ├── app-installer-ui-dialog.png │ ├── app-installer-zone-error.png │ ├── appinstaller-screen.png │ ├── aws-app-cert.png │ ├── aws-package-path.png │ ├── aws-permissions.png │ ├── aws-post-create.png │ ├── aws-upload-package.png │ ├── azure-create-app-2.png │ ├── azure-create-app.png │ ├── azure-new-file.png │ ├── azure-upload-file.png │ ├── custom-protocol.PNG │ ├── edge.png │ ├── packaging-screen2.jpg │ ├── packaging-screen5.jpg │ ├── run.png │ ├── sample-web-app.png │ ├── select-sideloading.png │ ├── sideloading-screen.png │ ├── web-page.png │ └── web-tab.png ├── install-parameters.md ├── install-update-app-installer.md ├── installing-windows10-apps-web.md ├── troubleshoot-appinstaller-issues.md ├── update-settings.md ├── web-install-IIS.md ├── web-install-aws.md └── web-install-azure.md ├── app-package-updates.md ├── breadcrumb └── toc.yml ├── comparisonofappvwithmsix.md ├── customer-journey.md ├── customer ├── db-systel.md ├── ecno.md ├── mid.md ├── sap.md ├── schneider-electric.md └── trend-micro.md ├── desktop ├── .desktop-to-uwp-behind-the-scenes.md.swp ├── app-attach-from-visualstudio.md ├── azure-dev-ops.md ├── before-packaging-overview.md ├── cicd-keyvault.md ├── cicd-overview.md ├── custom-props-app-extensions.md ├── deploy-preinstalled-apps.md ├── desktop-to-uwp-behind-the-scenes.md ├── desktop-to-uwp-debug.md ├── desktop-to-uwp-known-issues.md ├── desktop-to-uwp-manual-conversion.md ├── desktop-to-uwp-packaging-dot-net.md ├── desktop-to-uwp-prepare.md ├── desktop-to-uwp-r2r.md ├── desktop-to-uwp-test-windows-s.md ├── desktop-to-uwp-third-party-installer.md ├── extend-overview.md ├── flexible-virtualization.md ├── image2.png ├── image3.png ├── images │ ├── Advanced_Installer_Vertical.png │ ├── Advanced_Installer_Vertical_20.png │ ├── AppCure-WB.png │ ├── Capture-AccessIT.png │ ├── FG3rdPartyLogo.png │ ├── FG3rdPartyLogo_50.png │ ├── Infinity_logo.png │ ├── InstallShield-logo.jpg │ ├── PACE-suite-logos.png │ ├── PACE.png │ ├── PACE_20.png │ ├── RaynetLogo_v3.png │ ├── RaynetLogo_v3_20.png │ ├── Rimo3CLOUD-Logo-Colour-RGB.png │ ├── add-packaging-project.png │ ├── add-project-ref-2.png │ ├── add-project-ref.png │ ├── apptimized.png │ ├── bas-image-setup.png │ ├── ci-debug-setting.png │ ├── cicd-keyvault │ │ ├── add-access-policy.png │ │ ├── add-variable.png │ │ ├── advanced-settings.png │ │ ├── application-id.png │ │ ├── register-application.png │ │ └── select-principal.png │ ├── cloudhouse-container-logo.png │ ├── cloudhouse-container-logo_30.png │ ├── code-integrity-logs.png │ ├── config-manager.png │ ├── configure-x86.png │ ├── converted-app-installed.png │ ├── dac.png │ ├── desktop-bridge-4.png │ ├── developer-command-prompt.png │ ├── generated-cert-file.png │ ├── install-4.6.2-devpack.png │ ├── install.png │ ├── installaware.png │ ├── installaware_20.png │ ├── liquit_logo.png │ ├── msix-packaging-ext │ │ ├── add-task.png │ │ ├── agent-specification.png │ │ ├── app-attach.png │ │ ├── app-installer.png │ │ ├── browse-marketplace.png │ │ ├── build-and-package.png │ │ ├── classic-editor.png │ │ ├── empty-job.png │ │ ├── new-pipeline.png │ │ ├── select-pipeline.png │ │ ├── sign-with-cert.png │ │ ├── sign-with-kv.png │ │ ├── signing.png │ │ └── vcs.png │ ├── run-converter.png │ ├── set-as-entry-point.png │ ├── target-version.png │ ├── trusted-people-store.png │ ├── win-10-version.png │ ├── windows-app-package.png │ └── winver.png ├── managing-your-msix-deployment-configmgr.md ├── managing-your-msix-deployment-downgrading.md ├── managing-your-msix-deployment-enterprise.md ├── managing-your-msix-deployment-intune.md ├── managing-your-msix-deployment-mem-adminconsole.md ├── managing-your-msix-deployment-overview.md ├── managing-your-msix-deployment-retail.md ├── managing-your-msix-deployment-targetdevices.md ├── managing-your-msix-deployment-troubleshooting.md ├── managing-your-msix-deployment-update.md ├── managing-your-msix-reset-and-repair.md ├── media │ ├── app-attach-from-visualstudio │ │ ├── image.png │ │ ├── image1.png │ │ ├── screenshot-2023-05-30-165600.png │ │ ├── screenshot-2023-05-30-165836.png │ │ ├── screenshot-2023-10-11-180059.png │ │ ├── screenshot-2023-10-11-181102.png │ │ └── screenshot-2023-10-11-182632.png │ ├── desktop-to-uwp-packaging-dot-net │ │ └── microsoftteams-image-(12).png │ └── msix-packaging-extension │ │ ├── ado-extension-image1.png │ │ ├── ado-extension-image2.png │ │ └── ado-extension-image3.png ├── msix-packaging-extension.md ├── powershell-msix-cmdlets.md ├── register-from-network.md ├── sign-with-akv-cert.md ├── source-code-overview.md ├── tamper-protection.md ├── validation-overview.md └── vs-package-overview.md ├── detect-package-identity.md ├── docfx.json ├── group-policy-msix.md ├── images ├── AccessITAutomationLogoTransp.png ├── AccessItItAutomationLogoRebranded.png ├── AdvancedInstaller_Logo.png ├── AppCure-WB-fixed.png ├── AppCure-WB.png ├── Apptimized_Logo.png ├── Camwood_Logo.jpg ├── Camwood_Logo_2.png ├── CloudHouse_Logo.png ├── DB_logo_red_outlined_200px_rgb.png ├── ECNO_masterlogo.png ├── EMCO_Software_Logo.png ├── FireGiant_Logo.png ├── Flexera_Logo.png ├── InfoPulse_Logo.png ├── Logo-MIDGmbH.png ├── Logo_SE_Green_RGB-Screen.png ├── MPT-mod-page.png ├── MP_logo.png ├── PACE-Suite-white-for-dark-background-small.png ├── PACE-suite-logos.png ├── Pace_Logo.png ├── RayPackStudio_Logo.png ├── RayPackStudio_Logo_offset.png ├── Raynet_Logo.png ├── Revenera_light.png ├── Rimo3_Logo.png ├── SAP_R_grad.png ├── SSH2_Logo.png ├── Trend_Micro-lightmode.png ├── installAware_logo.png ├── liquit_logo.png ├── msix-bad-cert.png ├── msix-good-cert.png ├── readiness-logo-offset.png ├── readiness-logo.png └── start-comp-cert.png ├── index.yml ├── manage ├── create-directory.md ├── shared-package-container.md └── troubleshoot-msix-container.md ├── media └── partners │ └── app-v-scheduler-logo2.png ├── modification-packages.md ├── msix-container.md ├── msix-core ├── deploy-msix-core-app-with-configmgr.md ├── deploy-msix-core-with-configmgr.md ├── deploy-with-msix-core.md ├── msixcore-clickonce-solution.md ├── msixcore-troubleshoot.md ├── msixcore.md └── support-msix-core.md ├── msix-sdk ├── msix-linux.md ├── release-notes │ ├── sdk-release-notes-1.4.md │ ├── sdk-release-notes-1.5.md │ ├── sdk-release-notes-1.6.md │ └── sdk-release-notes-1.7.md ├── sdk-guidance.md └── sdk-overview.md ├── msix-server-2019.md ├── non-store-developer-updates.md ├── overview.md ├── package ├── app-package-formats.md ├── asset-packages.md ├── bundling-overview.md ├── create-app-package-with-makeappx-tool.md ├── create-certificate-package-signing.md ├── create-cgm.md ├── device-architecture.md ├── flat-bundles.md ├── fx-packages.md ├── images │ ├── appinstaller-screen.png │ ├── bundle-combined.png │ ├── msixpackage.png │ ├── package-signing2.PNG │ ├── packaging-layout.png │ ├── packaging-screen1.jpg │ ├── packaging-screen10.png │ ├── packaging-screen2.jpg │ ├── packaging-screen3.jpg │ ├── packaging-screen4.jpg │ ├── packaging-screen5.jpg │ ├── packaging-screen6.jpg │ ├── packaging-screen7.jpg │ ├── packaging-screen8.jpg │ ├── packaging-screen9.jpg │ └── primary-bundle.png ├── manual-packaging-root.md ├── modification-package-developers.md ├── optional-packages-with-executable-code.md ├── optional-packages.md ├── package-folding.md ├── packaging-layout.md ├── packaging-uwp-apps.md ├── persistent-identity.md ├── resource-package.md ├── sign-app-package-using-signtool.md ├── signing-known-issues.md ├── signing-package-device-guard-signing.md ├── signing-package-overview.md ├── streaming-install.md └── unsigned-package.md ├── packaging-tool ├── Quick-Create-VM.md ├── bundle-msix-packages.md ├── convert-an-installer-with-services.md ├── create-an-msix-overview.md ├── create-app-package.md ├── create-start-group.md ├── disconnected-environment.md ├── duplicate-tool-settings-across-devices.md ├── edit-icons-and-assets.md ├── generate-template-file.md ├── images │ ├── PackageEditorPkgInfo1.png │ ├── PackageEditorPkgInfo2.png │ ├── QuickCreateVM.png │ ├── bundle-pic1.png │ ├── mpt_blog_0.jpg │ ├── mpt_blog_1.jpg │ ├── mpt_blog_10.jpg │ ├── mpt_blog_11.jpg │ ├── mpt_blog_2.jpg │ ├── mpt_blog_3.jpg │ ├── mpt_blog_4.jpg │ ├── mpt_blog_5.jpg │ ├── mpt_blog_6.jpg │ ├── mpt_blog_7.jpg │ ├── mpt_blog_9.jpg │ ├── pic1.PNG │ ├── pic11.png │ ├── pic12.png │ ├── pic13.png │ ├── pic2.jpg │ ├── pic3.jpg │ ├── pic4.png │ ├── pic5.png │ ├── pic6.png │ ├── pic7.png │ ├── pic8.png │ └── pic9.png ├── insider-program.md ├── know-your-installer.md ├── media │ └── package-analyzer │ │ └── screenshot-2023-10-06-014557.jpg ├── package-analyzer.md ├── package-conversion-command-line.md ├── package-editor.md ├── prepare-your-environment.md ├── release-notes │ └── history.md ├── remote-conversion-setup.md ├── support-legacy-context-menus.md ├── support-restart.md ├── tool-best-practices.md ├── tool-known-issues.md └── tool-overview.md ├── partners.md ├── psf ├── create-package-support-framework.md ├── create-shortcut-with-script-package-support-framework.md ├── images │ ├── add-reference-packaging-project.png │ ├── appxmanifest-application-executable.png │ ├── appxmanifest-application-id.png │ ├── appxmanifest-application-processexecutable.png │ ├── appxmanifest-application-workingdirectory.png │ ├── blank-app.png │ ├── blank-solution.png │ ├── configjson-complete.png │ ├── contosoapp-fileproperties-target-parameter.png │ ├── contosoapp-fileproperties-target.png │ ├── contosoexpense-add-psf-files.png │ ├── contosoexpense-appdata-icon.png │ ├── contosoexpense-changevalues-shortcut.png │ ├── contosoexpense-config-json.png │ ├── contosoexpense-create-alias.png │ ├── contosoexpense-edit-manifest.png │ ├── contosoexpense-edit-mpt.png │ ├── contosoexpense-final-shortcut.png │ ├── contosoexpense-finish-creating-appshortcut.png │ ├── contosoexpense-generic-shortcut.png │ ├── contosoexpense-new-appshortcut.png │ ├── contosoexpense-newpath-shortcut.png │ ├── contosoexpense-psf-added-files.png │ ├── contosoexpense-psf-manifest.png │ ├── contosoexpense-run-through-alias.png │ ├── contosoexpense.png │ ├── get-psf-from-github-releases.png │ ├── iso-option.png │ ├── package-project-references.png │ ├── package-project-template.png │ ├── package-support-framework-2.png │ ├── package-support-framework.png │ ├── package_binaries.png │ ├── package_contents.png │ ├── procmon-filterdialog-completed.png │ ├── procmon-filterdialog-processname-psfsample.png │ ├── procmon-filterdialog-result-success.png │ ├── procmon-psfsampleapp-readfailure.png │ ├── procmon-psfsampleapp-writefailure.png │ ├── procmon_app_filter.png │ ├── procmon_config_txt.png │ ├── procmon_events.png │ ├── procmon_exclude_success.png │ ├── procmon_logfile.png │ ├── psf-package.png │ ├── psfsampleapp_config_txt.png │ ├── reference-fix.png │ ├── runtime-fix-library.png │ ├── runtime-fix-project-structure.png │ ├── set-startup-project.png │ ├── shim-exe-reference.png │ ├── traceshim_accessdenied.png │ └── traceshim_filenotfound.png ├── media │ └── psf-integration-with-mpt │ │ ├── psf-fixups-tab-in-mpt.jpg │ │ └── psf-fixups-tab-in-mpt1.jpg ├── package-support-framework-overview.md ├── package-support-framework-vs.md ├── package-support-framework.md ├── psf-current-working-directory.md ├── psf-filesystem-writepermission.md ├── psf-integration-with-mpt.md ├── psf-launch-apps-with-parameters.md └── run-scripts-with-package-support-framework.md ├── render.yml ├── resources.md ├── store-developer-package-update.md ├── supported-platforms.md ├── toc.yml └── toolkit ├── accelerators.md ├── msix-toolkit-appinstallerfilebuilder.md ├── msix-toolkit-modifypackagepublisher.md ├── msix-toolkit-msixbatchconversion.md └── msix-toolkit-overview.md /.gitattributes: -------------------------------------------------------------------------------- 1 | # Set the default behavior, in case people don't have core.autocrlf set. 2 | * text=auto 3 | 4 | # Explicitly declare text files you want to always be normalized and converted 5 | # to native line endings on checkout. 6 | *.c text 7 | *.h text 8 | 9 | # Declare files that will always have CRLF line endings on checkout. 10 | *.sln text eol=crlf 11 | 12 | # Denote all files that are truly binary and should not be modified. 13 | *.png binary 14 | *.jpg binary -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | log/ 2 | obj/ 3 | _site/ 4 | .optemp/ 5 | _themes*/ 6 | _repo.*/ 7 | .vscode/ 8 | .openpublishing.buildcore.ps1 -------------------------------------------------------------------------------- /.openpublishing.publish.config.json: -------------------------------------------------------------------------------- 1 | { 2 | "docsets_to_publish": [ 3 | { 4 | "docset_name": "msix", 5 | "build_source_folder": "msix-src", 6 | "build_output_subfolder": "msix", 7 | "locale": "en-us", 8 | "monikers": [], 9 | "moniker_ranges": [], 10 | "open_to_public_contributors": true, 11 | "type_mapping": { 12 | "Conceptual": "Content", 13 | "ManagedReference": "Content", 14 | "RestApi": "Content" 15 | }, 16 | "build_entry_point": "docs", 17 | "template_folder": "_themes" 18 | } 19 | ], 20 | "notification_subscribers": [], 21 | "sync_notification_subscribers": [], 22 | "branches_to_filter": [], 23 | "git_repository_url_open_to_public_contributors": "https://github.com/microsoftdocs/msix-docs", 24 | "git_repository_branch_open_to_public_contributors": "main", 25 | "skip_source_output_uploading": false, 26 | "need_preview_pull_request": true, 27 | "contribution_branch_mappings": {}, 28 | "dependent_repositories": [ 29 | { 30 | "path_to_root": "_themes", 31 | "url": "https://github.com/Microsoft/templates.docs.msft", 32 | "branch": "main", 33 | "branch_mapping": {} 34 | }, 35 | { 36 | "path_to_root": "_themes.pdf", 37 | "url": "https://github.com/Microsoft/templates.docs.msft.pdf", 38 | "branch": "main", 39 | "branch_mapping": {} 40 | } 41 | ], 42 | "branch_target_mapping": { 43 | "live": [ 44 | "Publish", 45 | "Pdf" 46 | ], 47 | "main": [ 48 | "Publish", 49 | "Pdf" 50 | ] 51 | }, 52 | "need_generate_pdf_url_template": true, 53 | "targets": { 54 | "pdf": { 55 | "template_folder": "_themes.pdf" 56 | } 57 | }, 58 | "docs_build_engine": { 59 | "name": "docfx_v3" 60 | } 61 | } -------------------------------------------------------------------------------- /LICENSE-CODE: -------------------------------------------------------------------------------- 1 | The MIT License (MIT) 2 | Copyright (c) Microsoft Corporation 3 | 4 | Permission is hereby granted, free of charge, to any person obtaining a copy of this software and 5 | associated documentation files (the "Software"), to deal in the Software without restriction, 6 | including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, 7 | and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, 8 | subject to the following conditions: 9 | 10 | The above copyright notice and this permission notice shall be included in all copies or substantial 11 | portions of the Software. 12 | 13 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT 14 | NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. 15 | IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, 16 | WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE 17 | SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | ## Microsoft Open Source Code of Conduct 2 | This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). 3 | For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments. 4 | 5 | -------------------------------------------------------------------------------- /SECURITY.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | ## Security 4 | 5 | Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [our GitHub organizations](https://opensource.microsoft.com/). 6 | 7 | If you believe you have found a security vulnerability in any Microsoft-owned repository that meets [Microsoft's definition of a security vulnerability](https://aka.ms/opensource/security/definition), please report it to us as described below. 8 | 9 | ## Reporting Security Issues 10 | 11 | **Please do not report security vulnerabilities through public GitHub issues.** 12 | 13 | Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://aka.ms/opensource/security/create-report). 14 | 15 | If you prefer to submit without logging in, send email to [secure@microsoft.com](mailto:secure@microsoft.com). If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://aka.ms/opensource/security/pgpkey). 16 | 17 | You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://aka.ms/opensource/security/msrc). 18 | 19 | Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue: 20 | 21 | * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.) 22 | * Full paths of source file(s) related to the manifestation of the issue 23 | * The location of the affected source code (tag/branch/commit or direct URL) 24 | * Any special configuration required to reproduce the issue 25 | * Step-by-step instructions to reproduce the issue 26 | * Proof-of-concept or exploit code (if possible) 27 | * Impact of the issue, including how an attacker might exploit the issue 28 | 29 | This information will help us triage your report more quickly. 30 | 31 | If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our [Microsoft Bug Bounty Program](https://aka.ms/opensource/security/bounty) page for more details about our active programs. 32 | 33 | ## Preferred Languages 34 | 35 | We prefer all communications to be in English. 36 | 37 | ## Policy 38 | 39 | Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://aka.ms/opensource/security/cvd). 40 | 41 | 42 | -------------------------------------------------------------------------------- /ThirdPartyNotices: -------------------------------------------------------------------------------- 1 | ##Legal Notices 2 | Microsoft and any contributors grant you a license to the Microsoft documentation and other content 3 | in this repository under the [Creative Commons Attribution 4.0 International Public License](https://creativecommons.org/licenses/by/4.0/legalcode), 4 | see the [LICENSE](LICENSE) file, and grant you a license to any code in the repository under the [MIT License](https://opensource.org/licenses/MIT), see the 5 | [LICENSE-CODE](LICENSE-CODE) file. 6 | 7 | Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation 8 | may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries. 9 | The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks. 10 | Microsoft's general trademark guidelines can be found at http://go.microsoft.com/fwlink/?LinkID=254653. 11 | 12 | Privacy information can be found at https://privacy.microsoft.com/ 13 | 14 | Microsoft and any contributors reserve all others rights, whether under their respective copyrights, patents, 15 | or trademarks, whether by implication, estoppel or otherwise. -------------------------------------------------------------------------------- /msix-src/app-installer/app-installer-api-issues.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: App Installer file API issues 3 | description: This article lists known issues with the PackageManager and Package APIs for managing App Installer files. 4 | ms.date: 2/20/2019 5 | ms.topic: article 6 | keywords: windows 10, uwp, app installer, AppInstaller, sideload, API 7 | ms.custom: 19H1 8 | --- 9 | 10 | # App Installer file API issues 11 | 12 | ## JavaScript support for App Installer file APIs 13 | 14 | The [PackageManager](/uwp/api/windows.management.deployment.packagemanager) and [Package](/uwp/api/windows.applicationmodel.package) classes in the Windows SDK provide methods you can use to add or modify packages via App Installer files or to retrieve information about apps with an App Installer association. For more information, see [Related documentation](app-installer-documentation.md). 15 | 16 | Of these methods, [PackageManager.AddPackageByAppInstallerFileAsync](/uwp/api/windows.management.deployment.packagemanager.addpackagebyappinstallerfileasync), [PackageManager.RequestAddPackageByAppInstallerFileAsync](/uwp/api/windows.management.deployment.packagemanager.requestaddpackagebyappinstallerfileasync), and [Package.CheckUpdateAvailabilityAsync](/uwp/api/windows.applicationmodel.package.checkupdateavailabilityasync) are not supported in JavaScript. However, you can create a [Windows Runtime component](/windows/uwp/winrt-components/walkthrough-creating-a-simple-windows-runtime-component-and-calling-it-from-javascript) that calls these methods and then call this component from a JavaScript UWP app. 17 | 18 | Here is an example. 19 | 20 | ```csharp 21 | namespace CSRuntimeComponent 22 | { 23 | public sealed class UpdateAvailabilityChecker 24 | { 25 | public static IAsyncOperation CheckForUpdatesAsync() 26 | { 27 | return AsyncInfo.Run((result) => Task.Run(async () => 28 | { 29 | PackageManager pm = new PackageManager(); 30 | Package currentPackage = pm.FindPackageForUser(string.Empty, Package.Current.Id.FullName); 31 | PackageUpdateAvailabilityResult apiResult = await currentPackage.CheckUpdateAvailabilityAsync(); 32 | 33 | if (apiResult.Availability == PackageUpdateAvailability.Error) 34 | { 35 | Logger.Error($"Error occurred, extended code: {apiResult.ExtendedError}"); 36 | } 37 | 38 | return apiResult.Availability; 39 | })); 40 | } 41 | } 42 | } 43 | ``` 44 | 45 | ```javascript 46 | window.onload = function () { 47 | document.getElementById('mainButton').onclick = function (evt) { 48 | CSRuntimeComponent.UpdateAvailabilityChecker.checkForUpdatesAsync().done(function (result) { 49 | document.getElementById("resultLabel").innerHTML = "Update availability result:" + result; 50 | }); 51 | } 52 | } 53 | ``` 54 | -------------------------------------------------------------------------------- /msix-src/app-installer/app-installer-authentication-manager--overview.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: App Installer Authentication Manager 3 | description: Overview of the App Installer Authentication Manager 4 | ms.date: 12/12/2023 5 | ms.topic: article 6 | keywords: windows 11, windows 10, uwp, app installer, AppInstaller 7 | --- 8 | 9 | # App Installer Authentication Manager 10 | 11 | The Microsoft Desktop App Installer on Windows 11 supports OAuth 2.0 authentication requests for identities hosted in Microsoft Azure Active Directory (AAD) to access the Windows app installation media. The user will only be prompted for authentication if the Windows app installation media is inaccessible, by first attempting to access the media for display to the user. 12 | 13 | If authentication is required, the URI targeting the installation media must provide the identity hosting solution by including the suffix of `?msixauth=` to the URI. By specifying the identity provider, the Microsoft Desktop App Installer will connect to the desired identity provider to request authentication. 14 | 15 | | Identity Service | Identity Connection String | 16 | |-------------------|-----------------------------| 17 | | Microsoft AAD | msixauth=aad | 18 | 19 | > [!Note] 20 | > 1. The values of each field must be URL-encoded, that is with non-printing characters and spaces. The use of question mark ("?") to separate the main Source from the field values, and ampersands ("&") to separate each subsequent fields in the `ms-appinstaller:`. 21 | > Example: `ms-appinstaller:?source=https://website.com/app.msix&msixauth=aad` 22 | > 23 | > 2.The ability to use the *ms-appinstaller* URI (Uniform Resource Identifier) scheme (protocol) can be controlled by an IT professional (an administrator). To enable *ms-appinstaller* on your network, set the Group Policy **EnableMSAppInstallerProtocol** (/windows/client-management/mdm/policy-csp-desktopappinstaller) to enabled (see [Policy CSP - DesktopAppInstaller](/windows/client-management/mdm/policy-csp-desktopappinstaller#enablemsappinstallerprotocol)). For more info, see [Installing Windows 10 apps from a web page](/windows/msix/app-installer/installing-windows10-apps-web). 24 | -------------------------------------------------------------------------------- /msix-src/app-installer/app-installer-documentation.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Related App Installer file documentation 3 | description: This article provides links to documentation about the App Installer file schema and related APIs provided by the Windows SDK. 4 | ms.date: 2/20/2019 5 | ms.topic: article 6 | keywords: windows 10, uwp, app installer, AppInstaller, sideload, API, XML, schema 7 | ms.custom: 19H1 8 | --- 9 | 10 | # App Installer file APIs 11 | 12 | The [PackageManager](/uwp/api/windows.management.deployment.packagemanager) and [Package](/uwp/api/windows.applicationmodel.package) classes in the Windows SDK provide methods you can use to add or modify packages via App Installer files, or to retrieve information about apps with an App Installer association. 13 | 14 | | Method | Description | Minimum supported release | 15 | |----------|--------------|-------------------| 16 | | [PackageManager.AddPackageByAppInstallerFileAsync](/uwp/api/windows.management.deployment.packagemanager.addpackagebyappinstallerfileasync) | Allows single or multiple app packages to be installed with an .appinstaller file. | Windows 10 Fall Creators Update (version 1709, build 16299) | 17 | | [PackageManager.RequestAddPackageByAppInstallerFileAsync](/uwp/api/windows.management.deployment.packagemanager.requestaddpackagebyappinstallerfileasync) | Allows single or multiple app packages to be installed with an .appinstaller file. | Windows 10 Fall Creators Update (version 1709, build 16299) | 18 | | [Package.GetAppInstallerInfo](/uwp/api/windows.applicationmodel.package.getappinstallerinfo) | Returns the .appinstaller xml file location. This allows app developers to retrieve the .appinstaller xml file location when needed by their app. | Windows 10, version 1809 (build 17763) | 19 | | [Package.CheckUpdateAvailabilityAsync](/uwp/api/windows.applicationmodel.package.checkupdateavailabilityasync) | Checks for updates to the main app package listed in the .appinstaller file. It allows the developer to determine if the updates are required due to .appinstaller policy. This method currently only works for applications installed via .appinstaller files. | Windows 10, version 1809 (build 17763) | 20 | 21 | ## App Installer file schema 22 | 23 | For more information about how to manually format an App Installer file, see [App installer file schema reference](/uwp/schemas/appinstallerschema/app-installer-file). 24 | -------------------------------------------------------------------------------- /msix-src/app-installer/app-installer-ui-dialog.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: App Installer Dialog Elements 3 | description: This article provides information on the App Installer dialog. 4 | ms.date: 7/1/2024 5 | ms.topic: article 6 | keywords: windows 10, uwp, app installer, AppInstaller, sideload 7 | ms.custom: 19H1 8 | --- 9 | 10 | # App Installer User Interface 11 | The App Installer provides the user interface for installation of [MSIX packages](/windows/msix/overview). The interface is defined to provide the user with critical information about the package in order to make an informed decision about installing the application. 12 | 13 | The App Installer interface consist of the following features: 14 | 15 | * Application name 16 | * Application icon 17 | * Microsoft Store signature 18 | * Publisher name 19 | * Version 20 | * Source 21 | * Capabilities 22 | * Internet warning notification 23 | * Install and Cancel buttons 24 | * Launch when ready 25 | 26 | ![Smart Dialog](./images/app-installer-ui-dialog.png) 27 | 28 | ## Application name 29 | The application name is provided by the app author, and extracted from the [MSIX file.](/windows/msix/overview) 30 | 31 | ## Microsoft Store signature 32 | If the dialog shows the string, "Microsoft Store App", you know the application has been successfully built and distributed through the Microsoft Store. Microsoft Store Signed Apps have been tested and comply with the [Microsoft Store Policies](/windows/apps/publish/store-policies) 33 | 34 | ## Publisher name and Version 35 | The publisher name and version are provided by the app author, and extracted from the [MSIX file.](/windows/msix/overview) 36 | 37 | ## Source 38 | 39 | The source provides the domain of the URL that the package was sourced from. This allows the user to decide whether they trust the source when deciding whether to install the package. 40 | 41 | ## Capabilities 42 | The listing of the [capabilities](/windows/uwp/packaging/app-capability-declarations) allows the user to evaluate what the application can access on your PC before installing it. If the application is accessing a capability you do not agree with, it is recommended you choose cancel. 43 | 44 | ## Install and Cancel buttons 45 | 46 | The Install and Cancel buttons will generally be provided when installing applications. If you are downgrading an application or reinstalling the application, the text of the Install button will change to Reinstall. 47 | 48 | The Cancel button closes the dialog without making any changes. 49 | 50 | ## Launch when ready 51 | 52 | Because the App Installer improves the installation process, it can automatically start the app following installation. This is a check box control the user can uncheck. 53 | 54 | ## Internet Warning 55 | 56 | App Installer will display an internet application warning for applications that come from the internet. This warning informs the user to use caution when installing this application. As with any application installed from the internet, the user must use caution. Only install apps from trusted sources, such as Microsoft Store, and be thoughtful about which apps you install. 57 | See [Protect your PC from unwanted software](https://support.microsoft.com/windows/protect-your-pc-from-unwanted-software-074a2d74-02db-03dd-8340-9e1822377856) for more information. 58 | 59 | 60 | 61 | 62 | -------------------------------------------------------------------------------- /msix-src/app-installer/images/App-Installer-File-Update.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/app-installer/images/App-Installer-File-Update.png -------------------------------------------------------------------------------- /msix-src/app-installer/images/Install-asp.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/app-installer/images/Install-asp.png -------------------------------------------------------------------------------- /msix-src/app-installer/images/add-package.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/app-installer/images/add-package.png -------------------------------------------------------------------------------- /msix-src/app-installer/images/app-installer-smart-screen.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/app-installer/images/app-installer-smart-screen.png -------------------------------------------------------------------------------- /msix-src/app-installer/images/app-installer-ui-dialog-update.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/app-installer/images/app-installer-ui-dialog-update.png -------------------------------------------------------------------------------- /msix-src/app-installer/images/app-installer-ui-dialog.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/app-installer/images/app-installer-ui-dialog.png -------------------------------------------------------------------------------- /msix-src/app-installer/images/app-installer-zone-error.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/app-installer/images/app-installer-zone-error.png -------------------------------------------------------------------------------- /msix-src/app-installer/images/appinstaller-screen.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/app-installer/images/appinstaller-screen.png -------------------------------------------------------------------------------- /msix-src/app-installer/images/aws-app-cert.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/app-installer/images/aws-app-cert.png -------------------------------------------------------------------------------- /msix-src/app-installer/images/aws-package-path.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/app-installer/images/aws-package-path.png -------------------------------------------------------------------------------- /msix-src/app-installer/images/aws-permissions.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/app-installer/images/aws-permissions.png -------------------------------------------------------------------------------- /msix-src/app-installer/images/aws-post-create.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/app-installer/images/aws-post-create.png -------------------------------------------------------------------------------- /msix-src/app-installer/images/aws-upload-package.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/app-installer/images/aws-upload-package.png -------------------------------------------------------------------------------- /msix-src/app-installer/images/azure-create-app-2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/app-installer/images/azure-create-app-2.png -------------------------------------------------------------------------------- /msix-src/app-installer/images/azure-create-app.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/app-installer/images/azure-create-app.png -------------------------------------------------------------------------------- /msix-src/app-installer/images/azure-new-file.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/app-installer/images/azure-new-file.png -------------------------------------------------------------------------------- /msix-src/app-installer/images/azure-upload-file.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/app-installer/images/azure-upload-file.png -------------------------------------------------------------------------------- /msix-src/app-installer/images/custom-protocol.PNG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/app-installer/images/custom-protocol.PNG -------------------------------------------------------------------------------- /msix-src/app-installer/images/edge.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/app-installer/images/edge.png -------------------------------------------------------------------------------- /msix-src/app-installer/images/packaging-screen2.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/app-installer/images/packaging-screen2.jpg -------------------------------------------------------------------------------- /msix-src/app-installer/images/packaging-screen5.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/app-installer/images/packaging-screen5.jpg -------------------------------------------------------------------------------- /msix-src/app-installer/images/run.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/app-installer/images/run.png -------------------------------------------------------------------------------- /msix-src/app-installer/images/sample-web-app.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/app-installer/images/sample-web-app.png -------------------------------------------------------------------------------- /msix-src/app-installer/images/select-sideloading.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/app-installer/images/select-sideloading.png -------------------------------------------------------------------------------- /msix-src/app-installer/images/sideloading-screen.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/app-installer/images/sideloading-screen.png -------------------------------------------------------------------------------- /msix-src/app-installer/images/web-page.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/app-installer/images/web-page.png -------------------------------------------------------------------------------- /msix-src/app-installer/images/web-tab.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/app-installer/images/web-tab.png -------------------------------------------------------------------------------- /msix-src/app-installer/install-update-app-installer.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Install and update the App Installer 3 | description: How to install and update the App Installer 4 | ms.date: 12/20/2023 5 | ms.topic: article 6 | keywords: windows 11, windows 10, uwp, app installer, AppInstaller, install, update 7 | --- 8 | 9 | # Installing the App Installer 10 | 11 | The App Installer ships as part of Windows. It allows for easy installation of MSIX files and MSIXBundles. 12 | 13 | If updates are enabled on a PC, then the App Installer will be updated automatically from the Microsoft Store. If the App Installer doesn't update, then you can use the troubleshooting tips at [Fix problems with apps from the Microsoft Store](https://support.microsoft.com/account-billing/fix-problems-with-apps-from-microsoft-store-93ed0bcf-9c12-3df6-6dda-92ec5d0415ac). 14 | 15 | If your PC doesn't have access to the Microsoft Store, then use the download button below 16 | 17 | > [!div class="button" style="text-align: left;" width="150px;"] 18 | > [Download the installer for the latest version of App Installer](https://aka.ms/getwinget) 19 | 20 | ## Use the winget tool to update 21 | 22 | Winget can update App Installer for you. At the command prompt, just type `winget upgrade Microsoft.AppInstaller`. 23 | 24 | ## Which version do I have? 25 | 26 | You can use this PowerShell command to determine the version of App Installer that you have installed: 27 | 28 | ```powershell 29 | (Get-AppxPackage Microsoft.DesktopAppInstaller).Version 30 | ``` 31 | -------------------------------------------------------------------------------- /msix-src/app-installer/update-settings.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: App Installer file update settings 3 | description: This article describes options for how to configure the behavior of app updates by using the App Installer file. 4 | ms.date: 06/12/2020 5 | ms.topic: article 6 | keywords: windows 10, uwp, msix 7 | ms.custom: RS5 8 | --- 9 | 10 | # Configure update settings in the App Installer file 11 | 12 | As mentioned in [App Installer file overview](app-installer-file-overview.md), you can configure the update behavior of the app in the App Installer file. This article explores the update options and their respective trade-offs. 13 | 14 | You can configure the update behavior of the app by using the [UpdateSettings](/uwp/schemas/appinstallerschema/element-update-settings) element. Here we explore the update options and their respective trade-offs. 15 | 16 | In short, you can choose to check for updates two different ways: 17 | 1. Independently of the user launching the app. 18 | 2. Only when the user launches the app. 19 | 20 | Additionally, you can choose to apply updates in two different ways: 21 | 1. By informing the user with a prompt. 22 | 2. Silently, without informing the user. 23 | 24 | Finally, when you inform the user of an update, you can either force them to take the update before allowing them to launch the app, or you can allow them to launch the app and apply the update at an opportune time. 25 | 26 | 27 | The [UpdateSettings](/uwp/schemas/appinstallerschema/element-update-settings) element can have the following child elements: 28 | 29 | | App Installer file update setting | Min Windows 10 Version 30 | |------------------|--------------------| 31 | | OnLaunch| 1709 | 32 | | HoursBetweenUpdateChecks| 1803 | 33 | | AutomaticBackgroundTask | 1803 | 34 | | UpdateBlocksActivation | 1903 | 35 | | ShowPrompt | 1903 | 36 | | ForceUpdateFromAnyVersion | 1903 | 37 | 38 | - **OnLaunch**: Checks for updates on launch. This type of update can show UI and has the following attributes: 39 | 40 | - **HoursBetweenUpdateChecks**: An integer that indicates how often (in how many hours) the system will check for updates to the app. “0” to “255” inclusive. The default value is 24 (if this value is not specified). For example if HoursBetweenUpdateChecks = 3 then when the user launches the app, if the system has not checked for updates within the past 3 hours, it will check for updates now. 41 | 42 | - **ShowPrompt**: A boolean that determines if UI will be shown to the user. This value is supported on Windows 10, version 1903 and later. 43 | 44 | - **UpdateBlocksActivation**: A boolean that determines if the UI shown to the user allows the user to launch the app without taking the update, or if the user must take the update before launching the app. This attribute can be set to “true” only if **ShowPrompt** is set to “true”. **UpdateBlocksActivation**=“true” means the UI the user will see, allows the user to take the update or close the app. **UpdateBlocksActivation**="false" means the UI the user will see, allows the user to take the update or start the app without updating. In the latter case, the update will be applied silently at an opportune time. This value is supported on Windows 10, version 1903 and later. 45 | 46 | > [!NOTE] 47 | > ShowPrompt needs to be set to true if UpdateBlocksActivation is set to true. 48 | 49 | - **AutomaticBackgroundTask**: Checks for updates in the background every 8 hours independently of whether the user launched the app. This type of update cannot show UI. 50 | 51 | - **ForceUpdateFromAnyVersion**: Allows the app to update from version x to version x++ or to downgrade from version x to version x--. Without this element, the app can only move to a higher version. 52 | -------------------------------------------------------------------------------- /msix-src/breadcrumb/toc.yml: -------------------------------------------------------------------------------- 1 | - name: Windows 2 | tocHref: /windows/ 3 | topicHref: /windows/index 4 | items: 5 | - name: MSIX 6 | tocHref: /windows/msix/ 7 | topicHref: /windows/msix/index 8 | -------------------------------------------------------------------------------- /msix-src/comparisonofappvwithmsix.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Feature-based comparison of Application Virtualization and MSIX 3 | description: side-by-side comparison of App Virtualization (App-V) and MSIX 4 | author: fiza-azmi 5 | ms.author: fizaazmi 6 | ms.topic: product-comparison 7 | ms.date: 04/05/2023 8 | --- 9 | 10 | # Feature-based comparison of Application Virtualization and MSIX 11 | 12 | Application Virtualization (App-V) will be end-of-life in April 2026 (see [Microsoft Desktop Optimization Pack (MDOP) support extended](/lifecycle/announcements/mdop-extended)). As an alternative, we recommend that you look at *Azure Virtual Desktop with MSIX App Attach*. This article contains a side-by-side comparison of App Virtualization (App-V) and MSIX. 13 | 14 | ## Compare the features of App-V and MSIX 15 | 16 | This table compares the basic features of App-V with MSIX: 17 | 18 | |Feature|App-V|MSIX| 19 | | -------- | -------- | -------- | 20 | |Sharing across apps |A connection group feature in App-V groups packages together to create a virtual environment. This allows applications within that package group to interact with each other.|Shared package containers in MSIX allow IT Pros to create a shared runtime container for packaged application. This enables sharing a merged view of the virtual file system and virtual registry, thus providing access to one another's package root files and state. | 21 | |Development focus |End-of-life is April 2026.|Relatively newer; introduced in 2018.| 22 | |How updates are handled |App-V divides the app into 64KB blocks; however, the complete app needs to be downloaded in order to get the updates.|Only the delta (differential updates) are downloaded. | 23 | |A single copy of a file across apps/users |File duplication across apps isn't avoided. |A single copy of any file is kept.| 24 | |Signing |Not required|Required| 25 | 26 | ## For more info 27 | 28 | Learn more about Azure Virtual Desktop at [What is Azure Virtual Desktop?](/azure/virtual-desktop/overview). 29 | 30 | Learn more about MSIX app attach at [What is MSIX app attach?](/azure/virtual-desktop/what-is-app-attach). 31 | -------------------------------------------------------------------------------- /msix-src/customer-journey.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Links to customer journeys 3 | description: Get links to articles that describe DB Systel, ECNO, MID, SAP, Schneider Electric, and Trend Micro MSIX customer journeys. 4 | author: andreww-msft 5 | ms.date: 05/11/2022 6 | ms.topic: landing-page 7 | keywords: windows 10, uwp, msix 8 | ms.custom: RS5, kr2b-contr-experiment 9 | --- 10 | 11 | # Customer journeys with MSIX 12 | 13 | The following articles describe how customers successfully used MSIX to improve their Windows application deployments: 14 | 15 | - [DB Systel](customer/db-systel.md) used MSIX to enable agile Windows application deployment. 16 | - [Educational Computing Network of Ontario (ECNO)](customer/ecno.md) improved the desktop application delivery and install experience for Ontario students. 17 | - [MID GmbH](customer/mid.md) used MSIX and .NET Core to improve the release cycle of their Innovator Enterprise Modeling Suite. 18 | - [SAP](customer/sap.md) used Microsoft technology to save costs by improving their Windows application distribution mechanism. 19 | - [Schneider Electric](customer/schneider-electric.md) developed and deployed WPF desktop applications. 20 | - [Trend Micro](customer/trend-micro.md) used C++/WinRT and MSIX in Cleaner One. 21 | -------------------------------------------------------------------------------- /msix-src/customer/ecno.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: ECNO 3 | description: ECNO describes their experience with MSIX 4 | author: andreww-msft 5 | ms.date: 06/25/2020 6 | ms.topic: article 7 | keywords: windows 10, uwp, msix 8 | ms.custom: RS5 9 | --- 10 | 11 | # ECNO 12 | 13 | ![ECNO logo](../images/ECNO_masterlogo.png) 14 | 15 | The Educational Computing Network of Ontario (ECNO) is an organization that collaboratively finds and executes effective IT solutions for Ontario’s 72 K-12 school boards (2 million students). ECNO is tasked with keeping up on the latest computing technologies as they relate to the education goals of province of Ontario. They make IT infrastructure recommendations to and share best practices with the member school boards. 16 | 17 | The school boards are autonomous and are free to implement their own IT strategies for what works best for them. For example, one school board uses Configuration Manager exclusively to distribute applications, while another uses it only for machine imaging and a small percentage of apps. 18 | 19 | Under the umbrella of ECNO, the Shared Technology Services Project Team evaluates, tests, and packages an app catalog of 450 third party apps for the spectrum of needs for K–12 students as well as staff. 20 | 21 | To date, the ECNO STS Team has converted most of their apps via the MSIX Packaging Tool and the Bulk Conversion tool included in the MSIX Toolbox. 22 | 23 | ECNO currently has around 170 apps in Partner Center, with ten school boards linked to their LOB account. Two are currently allowing access on a ‘self-service’ basis to our apps in their store. The third has Configuration Manager linked to their store already and is looking to add access to our apps that way. Six more are looking to move into software management/assignment via Intune and has requested some sample apps to work with. And another school board is finishing a project to move their iPads into Intune as an MDM tool and then will be moving Windows devices into Intune (where they are looking at using MSIX and the store as their software distribution model). They expect more boards to start switching over as they move to adopt Intune/Configuration Manager. 24 | 25 | *"It’s a push in the right direction for us to deliver software to our users that are not able to be on a school network at this time during COVID-19. AppV packages have been a boon to us for years and this next iteration using MSIX will allow us to service our staff and students with the software they require using a delivery system that is modern and seamless from any internet connection in the world."* 26 | -Jason David Flannery, Systems Engineer, Simcoe County District School Board 27 | 28 | It’s easy to configure and easy to deploy once we enrolled devices into Windows Intune using autopilot. 29 | 30 | What benefits ECNO is getting by leveraging MSIX? 31 | 32 | * As a leader in software deployment for the school boards in Ontario, MSIX has provided a seamless transition from our App-V processes. 33 | * Allows our school boards to keep current in modern software deployment tools and end-point management. 34 | * For our project team it has increased productivity, provided easier deployment and support for our school boards. 35 | 36 | *"As our IT team strives to become more agile, especially now with distance learning upon us, we are relying on the cloud more and more. The next logical evolution for our organization is cloud management. We want our school based IT staff to focus more on the successful implementation of technology, less on deployment and troubleshooting. As we work towards zero touch deployment of our devices and apps we will be working closely with ECNO's STS team to integrate the apps we all use in the classroom into our cloud managed approach."* 37 | -Sean Heuchert, Manager of Information, Peterborough Victoria Northumberland Clarington Catholic District School Board 38 | -------------------------------------------------------------------------------- /msix-src/customer/sap.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: SAP 3 | description: SAP describes their experience with MSIX 4 | author: andreww-msft 5 | ms.date: 03/05/2021 6 | ms.topic: article 7 | keywords: windows 10, uwp, msix 8 | ms.custom: RS5 9 | --- 10 | # SAP 11 | 12 | ![SAP Logo](../images/SAP_R_grad.png) 13 | 14 | SAP is a software corporation that makes enterprise software to manage business operations and customer relations. SAP is headquartered in Walldorf, Germany with regional offices in 180 countries. 15 | 16 | Like many enterprises SAP faces a challenge to find the middle ground between allowing users to easily install the Apps they need on Windows, while limiting the permissions to what the user needs on the device, to prevent users from installing non-trusted (and potential harmful) applications, which will eventually cause the all known Windows “Rot” (aka Registry Rot), and would become a bigger issues for an Enterprise, as it translates into IT support tickets for each device that’s not behaving properly and at the end might even require the device to be re-imaged. 17 | 18 | As part of the digital transformation at SAP, and to address the previous challenge SAP has started a journey to move their Applications to a modern packaging format: MSIX; which is a Windows app package format that provides a modern packaging experience to all Windows apps. The MSIX package format preserves the functionality of existing app packages and/or install files in addition to enabling new, modern packaging and deployment features to Win32, WPF, and Windows Forms apps. 19 | 20 | By leveraging MSIX and Intune capabilities, SAP will be able to deploy the LOB Applications to SAP employees while removing unneeded additional users’ privileges on Windows devices at the same time. One of their goals is to provide a consistent App deployment experience without worrying who is installing the app. Removing Admin privileges to users that don’t need to have that permission, while allowing them to install the apps they need, will help SAP reduce IT tickets for Windows Devices PCs not working after the user installs applications, 21 | 22 | *“We have been successful in our MSIX Pilot so far and we believe it will help our organization to reduce IT support costs and improve our App delivery experience to end users. Thanks to the team for the help for the pilot”* -Eugene Schrempf, Global Head of Workplace Delivery at SAP Americas, Inc. 23 | 24 | -------------------------------------------------------------------------------- /msix-src/customer/schneider-electric.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Schneider Electric 3 | description: Schneider Electric describes their experience with MSIX 4 | author: andreww-msft 5 | ms.date: 06/25/2020 6 | ms.topic: article 7 | keywords: windows 10, uwp, msix 8 | ms.custom: RS5 9 | --- 10 | # Schneider Electric 11 | 12 | ![Schneider Electric](../images/Logo_SE_Green_RGB-Screen.png) 13 | 14 | Schneider Electric develops GIS software to support both small and large utilities (electric, gas, water, fiber, coax) within the US and internationally. 15 | 16 | In working with Microsoft, we wanted to bring our WPF applications to the latest installer technology, MSIX. We have a specific client-driven use case; we need to release and deploy frequently as a dev-ops minded software company, but each utility company wants to manage changes and individually determine what version of the application will be released to their users and when. We have been working closely with Microsoft to meet this customer requirement. After we complete our upgrade to MSIX we will be able to remove some 3rd party dependencies and be a step closer to updating our applications to .NET Core 3.0. 17 | 18 | By leveraging MSIX, we are simplifying our development stack. We will be using Microsoft technologies from code (C#/WPF) to build (Azure Dev Ops) to installer (MSIX). One of the key benefits of MSIX is that developers can easily develop, debug and test the installer directly from Visual Studio. This greatly simplifies installation specific troubleshooting and has allowed us to work closely with Microsoft. 19 | 20 | *"The support from Microsoft as we move to MSIX has been invaluable. We have a unique use case and Microsoft has helped us navigate any obstacles we encountered as we updated our applications. The developers are all excited to move our applications to MSIX."* –Darlene Rouleau from Schneider Electric 21 | -------------------------------------------------------------------------------- /msix-src/customer/trend-micro.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Trend Micro 3 | description: TREND Micro describes their experience with MSIX 4 | author: andreww-msft 5 | ms.date: 03/10/2021 6 | ms.topic: article 7 | keywords: windows 10, uwp, msix 8 | ms.custom: RS5 9 | --- 10 | # Trend Micro 11 | 12 | ![Trend Micro logo](../images/Trend_Micro-lightmode.png) 13 | 14 | Trend Micro Incorporated., a global leader in cybersecurity, helps to make the world safe for exchanging digital information. In an increasingly connected world, our innovative solutions for businesses, governments, and consumers provide layered security for data centers, cloud environments, networks, and endpoints. 15 | 16 | Besides the security sector, we are also looking for new opportunities in other domains, such as system maintenance and optimization. For example, we are developing Cleaner One, an innovative app to help users gain more free disk space (by removing junks, big files, duplicate files, etc.) and optimize their computer performance. At present, Cleaner One has two distribution channels, Microsoft Store and Online. 17 | 18 | During our development, we faced some challenges and finally resolved them by using new Windows development technologies. 19 | 20 | Previously, Cleaner One Store Version was developed for the Universal Windows Platform (UWP); Online Version was a desktop app adopting Win32 tech. It was difficult to maintain two different code branches. In order to unify both branches, we chose and applied Electron and Windows Packaging (Desktop Bridge), and it worked out well in practice. Furthermore, by leveraging C++/WinRT, we successfully implemented Windows 10 “Windows Toast Notification” and “Startup Task” APIs in the unified version. 21 | 22 | In Cleaner One, Electron includes Chromium Engine whose package size is large, making downloading and upgrading the whole package difficult, especially when there are network connection issues. Since MSIX is a modern packaging method on Windows and supports Incremental Upgrading well, with the help of MS Windows AppConsult, we started implementing MSIX packaging, which helps a lot not only on incremental upgrading, but also on simplifying CI/CD in our DevOps pipeline. Now Windows modern packaging runs smoothly in our environment. Meanwhile, our Online Version of product package can even benefit from MSIX. 23 | 24 | With these technologies, we helped our users and improved our acquisitions as well. 25 | - By leveraging Windows Packaging, we unified our code branches of Store Version and Online Version. 26 | - By integrating “Windows Toast Notification” API, we delivered better and more consistent user experience with less interference. 27 | - By integrating “Startup Task” API, we provided users the option to enable or disable Cleaner One. We used to get lots of user concerns regarding the ability to control auto startup of the app. 28 | - By using MSIX, we are able to make our product modernized in deployment, improve upgrade experience for users, and simplify our DevOps pipeline properly. 29 | 30 | *“MSIX and WinRT both are exciting techs for us. MSIX unifies the format of our Store Version and Online Version, makes packaging and deployment easier for developers. I am hoping that we can further digest MSIX and use it to empower our deployment process. Compared to Win32 API, C++/WinRT is object-oriented, powerful and yet easier to understand. More importantly, it not only supports UWP apps, but also gives us the opportunity to use latest Windows 10 techs in traditional Windows apps.”* - Developer Leader, Trend Micro 31 | -------------------------------------------------------------------------------- /msix-src/desktop/.desktop-to-uwp-behind-the-scenes.md.swp: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/.desktop-to-uwp-behind-the-scenes.md.swp -------------------------------------------------------------------------------- /msix-src/desktop/before-packaging-overview.md: -------------------------------------------------------------------------------- 1 | --- 2 | Description: An overview of topics to know before building an MSIX package 3 | title: Key concepts to know before packing to MSIX 4 | ms.date: 01/27/2020 5 | ms.topic: article 6 | keywords: windows 10, uwp 7 | ms.custom: RS5 8 | --- 9 | 10 | # What to know before packaging your desktop application 11 | 12 | This section contains requirements for a desktop app to run successfully as an MSIX package, and how a packaged desktop application interacts with Windows once packaged. This is useful to know before you begin the packaging process. If you're building a UWP app you can skip the sections on desktop applications below. 13 | 14 | |Topic| Description | 15 | |:---|:---| 16 | |[Preparing to package your desktop application](desktop-to-uwp-prepare.md)| A list of requirements for a desktop application to run successfully once packaged as MSIX. | 17 | |[How packaged desktop apps run on Windows](desktop-to-uwp-behind-the-scenes.md)| A deeper dive into what happens to file system and registry entries when you package your Desktop application as MSIX. | 18 | |[Flexible virtualization](flexible-virtualization.md)| The flexible virtualization feature provides a way for your app to declare that *some set* of its files and Registry entries should be visible to other apps; and that those should persist on app uninstall. *All other* files and Registry entries are not visible to other apps; and are removed on uninstall. | 19 | |[Bundling MSIX Packages](../package/bundling-overview.md)| This section gives an overview of bundling multiple MSIX packages into a single .msixbundle.| 20 | -------------------------------------------------------------------------------- /msix-src/desktop/cicd-overview.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: An overview of CI/CD solutions for MSIX app development 3 | title: MSIX and CI/CD Pipeline Overview 4 | ms.date: 01/11/2021 5 | ms.topic: article 6 | keywords: windows 10, uwp 7 | ms.custom: RS5 8 | --- 9 | 10 | # MSIX and CI/CD Pipeline Overview 11 | 12 | You can use Azure Pipelines to create automated builds for your MSIX project in Azure DevOps by either using the Azure DevOps extension: *MSIX Packaging* Extension or by configuring your own yaml file. We’ll also show you how to perform these tasks by using the command line so that you can integrate with any other build system. 13 | 14 | ## Create a new Azure Pipeline 15 | 16 | Begin by [signing up for Azure Pipelines](/azure/devops/pipelines/get-started/pipelines-sign-up) if you haven't done so already. 17 | 18 | Next, create a pipeline that you can use to build your source code. For a tutorial about building a pipeline to build a GitHub repository, see [Create your first pipeline](/azure/devops/pipelines/get-started-yaml). Azure Pipelines supports the repository types listed [in this article](/azure/devops/pipelines/repos). 19 | 20 | To set up the actual build pipeline, you browse to the Azure DevOps portal at dev.azure.com/\ and create a new project. If you don’t have an account, you can create one for free. Once you’ve signed in and created a project, you can either push the source code to the Git repository that’s set up for you at https://\@dev.azure.com//\/_git/\, or use any other provider, such as GitHub. You’ll get to choose the location of your repository when you create a new pipeline in the portal by clicking first on the **Pipelines** button and then on **New Pipeline**. 21 | 22 | 23 | ## Add your project certificate to the Secure files library 24 | 25 | > [!NOTE] 26 | >You should avoid submitting certificates to your repo if at all possible, and git ignores them by default. To manage the safe handling of sensitive files like certificates, Azure DevOps supports the [secure files](/azure/devops/pipelines/library/secure-files&preserve-view=true) feature. 27 | 28 | To upload a certificate for your automated build: 29 | 30 | 1. In Azure Pipelines, expand **Pipelines** in the navigation pane and click **Library**. 31 | 2. Click the **Secure files** tab and then click **+ Secure file**. 32 | 3. Browse to the certificate file and click **OK**. 33 | 4. After you upload the certificate, select it to view its properties. Under **Pipeline permissions**, enable the **Authorize for use in all pipelines** toggle. 34 | 5. If the private key in the certificate has a password, we recommend that you store your password in [Azure Key Vault](/azure/key-vault/about-keys-secrets-and-certificates) and then link the password to a [variable group](/azure/devops/pipelines/library/variable-groups). You can use the variable to access the password from the pipeline. Note that a password is only supported for the private key; using a certificate file that is itself password-protected is not currently supported. 35 | 36 | > [!NOTE] 37 | > Starting in Visual Studio 2019, a temporary certificate is no longer generated in MSIX projects. To create or export certificates, use the PowerShell cmdlets described in [this article](../package/create-certificate-package-signing.md). 38 | 39 | ## Configure your pipeline 40 | | Topic | Description | 41 | |----------|-----------| 42 | | [MSIX Packaging Extension](msix-packaging-extension.md) | Leverage the Azure DevOps extension that will guide you through building and signing an MSIX package | 43 | | [Configure CI/CD pipeline with YAML file](azure-dev-ops.md) | Configure your own yaml file | 44 | -------------------------------------------------------------------------------- /msix-src/desktop/extend-overview.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: An overview of topics for creating an MSIX package from source code. 3 | title: Building an MSIX package from your code 4 | ms.date: 01/27/2020 5 | ms.topic: article 6 | keywords: windows 10, uwp 7 | ms.custom: RS5 8 | --- 9 | 10 | # Extend your packaged applications 11 | 12 | MSIX makes it easy to extend your application using app extensions and optional packages. App extensions provide functionality similar to what plug-ins, add-ins, and add-ons do on other platforms. You can make your application an extension host to allowing it to consume content and deployment events from an extension packaged. App extensions were introduced in the Windows 10 Anniversary edition (version 1607, build 10.0.14393). 13 | 14 | Optional packages are useful for dividing a large or complex app, or adding new components to an app that's already been published. With Visual Studio 2017, version 15.7 and .NET Native 2.1, you can load executable code from both C++ and C# optional packages. 15 | 16 | App extensions are an open ecosystem and are intended for anyone to enhance your app. There is no gating or control over who gets to make an app extension. Optional packages are a closed ecosystem where you as the publisher decides who is allowed to make an optional package for your main package. 17 | 18 | App extensions are also independent packages. They can be standalone apps and cannot have a deployment dependency on another app. Optional packages require the primary package and cannot run without it. 19 | 20 | |Topic| Description | 21 | |:---|:---| 22 | |[Creating and hosting an app extension](/windows/uwp/launch-resume/how-to-create-an-extension?context=%252fwindows%252fmsix%252frender)|This section discusses how to create and host an app extension in your MSIX package. | 23 | [Custom properties for app extensions](custom-props-app-extensions.md)|This section discusses how to use custom properties for app extensions. | 24 | |[Extending your app using optional packages](../package/optional-packages-with-executable-code.md)| This section discusses how to take advantage of the optional package model to load content into your main package. | 25 | -------------------------------------------------------------------------------- /msix-src/desktop/image2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/image2.png -------------------------------------------------------------------------------- /msix-src/desktop/image3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/image3.png -------------------------------------------------------------------------------- /msix-src/desktop/images/Advanced_Installer_Vertical.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/Advanced_Installer_Vertical.png -------------------------------------------------------------------------------- /msix-src/desktop/images/Advanced_Installer_Vertical_20.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/Advanced_Installer_Vertical_20.png -------------------------------------------------------------------------------- /msix-src/desktop/images/AppCure-WB.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/AppCure-WB.png -------------------------------------------------------------------------------- /msix-src/desktop/images/Capture-AccessIT.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/Capture-AccessIT.png -------------------------------------------------------------------------------- /msix-src/desktop/images/FG3rdPartyLogo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/FG3rdPartyLogo.png -------------------------------------------------------------------------------- /msix-src/desktop/images/FG3rdPartyLogo_50.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/FG3rdPartyLogo_50.png -------------------------------------------------------------------------------- /msix-src/desktop/images/Infinity_logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/Infinity_logo.png -------------------------------------------------------------------------------- /msix-src/desktop/images/InstallShield-logo.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/InstallShield-logo.jpg -------------------------------------------------------------------------------- /msix-src/desktop/images/PACE-suite-logos.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/PACE-suite-logos.png -------------------------------------------------------------------------------- /msix-src/desktop/images/PACE.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/PACE.png -------------------------------------------------------------------------------- /msix-src/desktop/images/PACE_20.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/PACE_20.png -------------------------------------------------------------------------------- /msix-src/desktop/images/RaynetLogo_v3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/RaynetLogo_v3.png -------------------------------------------------------------------------------- /msix-src/desktop/images/RaynetLogo_v3_20.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/RaynetLogo_v3_20.png -------------------------------------------------------------------------------- /msix-src/desktop/images/Rimo3CLOUD-Logo-Colour-RGB.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/Rimo3CLOUD-Logo-Colour-RGB.png -------------------------------------------------------------------------------- /msix-src/desktop/images/add-packaging-project.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/add-packaging-project.png -------------------------------------------------------------------------------- /msix-src/desktop/images/add-project-ref-2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/add-project-ref-2.png -------------------------------------------------------------------------------- /msix-src/desktop/images/add-project-ref.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/add-project-ref.png -------------------------------------------------------------------------------- /msix-src/desktop/images/apptimized.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/apptimized.png -------------------------------------------------------------------------------- /msix-src/desktop/images/bas-image-setup.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/bas-image-setup.png -------------------------------------------------------------------------------- /msix-src/desktop/images/ci-debug-setting.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/ci-debug-setting.png -------------------------------------------------------------------------------- /msix-src/desktop/images/cicd-keyvault/add-access-policy.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/cicd-keyvault/add-access-policy.png -------------------------------------------------------------------------------- /msix-src/desktop/images/cicd-keyvault/add-variable.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/cicd-keyvault/add-variable.png -------------------------------------------------------------------------------- /msix-src/desktop/images/cicd-keyvault/advanced-settings.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/cicd-keyvault/advanced-settings.png -------------------------------------------------------------------------------- /msix-src/desktop/images/cicd-keyvault/application-id.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/cicd-keyvault/application-id.png -------------------------------------------------------------------------------- /msix-src/desktop/images/cicd-keyvault/register-application.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/cicd-keyvault/register-application.png -------------------------------------------------------------------------------- /msix-src/desktop/images/cicd-keyvault/select-principal.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/cicd-keyvault/select-principal.png -------------------------------------------------------------------------------- /msix-src/desktop/images/cloudhouse-container-logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/cloudhouse-container-logo.png -------------------------------------------------------------------------------- /msix-src/desktop/images/cloudhouse-container-logo_30.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/cloudhouse-container-logo_30.png -------------------------------------------------------------------------------- /msix-src/desktop/images/code-integrity-logs.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/code-integrity-logs.png -------------------------------------------------------------------------------- /msix-src/desktop/images/config-manager.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/config-manager.png -------------------------------------------------------------------------------- /msix-src/desktop/images/configure-x86.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/configure-x86.png -------------------------------------------------------------------------------- /msix-src/desktop/images/converted-app-installed.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/converted-app-installed.png -------------------------------------------------------------------------------- /msix-src/desktop/images/dac.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/dac.png -------------------------------------------------------------------------------- /msix-src/desktop/images/desktop-bridge-4.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/desktop-bridge-4.png -------------------------------------------------------------------------------- /msix-src/desktop/images/developer-command-prompt.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/developer-command-prompt.png -------------------------------------------------------------------------------- /msix-src/desktop/images/generated-cert-file.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/generated-cert-file.png -------------------------------------------------------------------------------- /msix-src/desktop/images/install-4.6.2-devpack.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/install-4.6.2-devpack.png -------------------------------------------------------------------------------- /msix-src/desktop/images/install.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/install.png -------------------------------------------------------------------------------- /msix-src/desktop/images/installaware.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/installaware.png -------------------------------------------------------------------------------- /msix-src/desktop/images/installaware_20.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/installaware_20.png -------------------------------------------------------------------------------- /msix-src/desktop/images/liquit_logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/liquit_logo.png -------------------------------------------------------------------------------- /msix-src/desktop/images/msix-packaging-ext/add-task.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/msix-packaging-ext/add-task.png -------------------------------------------------------------------------------- /msix-src/desktop/images/msix-packaging-ext/agent-specification.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/msix-packaging-ext/agent-specification.png -------------------------------------------------------------------------------- /msix-src/desktop/images/msix-packaging-ext/app-attach.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/msix-packaging-ext/app-attach.png -------------------------------------------------------------------------------- /msix-src/desktop/images/msix-packaging-ext/app-installer.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/msix-packaging-ext/app-installer.png -------------------------------------------------------------------------------- /msix-src/desktop/images/msix-packaging-ext/browse-marketplace.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/msix-packaging-ext/browse-marketplace.png -------------------------------------------------------------------------------- /msix-src/desktop/images/msix-packaging-ext/build-and-package.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/msix-packaging-ext/build-and-package.png -------------------------------------------------------------------------------- /msix-src/desktop/images/msix-packaging-ext/classic-editor.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/msix-packaging-ext/classic-editor.png -------------------------------------------------------------------------------- /msix-src/desktop/images/msix-packaging-ext/empty-job.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/msix-packaging-ext/empty-job.png -------------------------------------------------------------------------------- /msix-src/desktop/images/msix-packaging-ext/new-pipeline.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/msix-packaging-ext/new-pipeline.png -------------------------------------------------------------------------------- /msix-src/desktop/images/msix-packaging-ext/select-pipeline.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/msix-packaging-ext/select-pipeline.png -------------------------------------------------------------------------------- /msix-src/desktop/images/msix-packaging-ext/sign-with-cert.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/msix-packaging-ext/sign-with-cert.png -------------------------------------------------------------------------------- /msix-src/desktop/images/msix-packaging-ext/sign-with-kv.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/msix-packaging-ext/sign-with-kv.png -------------------------------------------------------------------------------- /msix-src/desktop/images/msix-packaging-ext/signing.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/msix-packaging-ext/signing.png -------------------------------------------------------------------------------- /msix-src/desktop/images/msix-packaging-ext/vcs.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/msix-packaging-ext/vcs.png -------------------------------------------------------------------------------- /msix-src/desktop/images/run-converter.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/run-converter.png -------------------------------------------------------------------------------- /msix-src/desktop/images/set-as-entry-point.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/set-as-entry-point.png -------------------------------------------------------------------------------- /msix-src/desktop/images/target-version.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/target-version.png -------------------------------------------------------------------------------- /msix-src/desktop/images/trusted-people-store.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/trusted-people-store.png -------------------------------------------------------------------------------- /msix-src/desktop/images/win-10-version.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/win-10-version.png -------------------------------------------------------------------------------- /msix-src/desktop/images/windows-app-package.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/windows-app-package.png -------------------------------------------------------------------------------- /msix-src/desktop/images/winver.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/images/winver.png -------------------------------------------------------------------------------- /msix-src/desktop/managing-your-msix-deployment-configmgr.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: This guide provides instruction on how to create and deploy an MSIX app with Microsoft Endpoint Configuration Manager 3 | title: Microsoft Endpoint Configuration Manager 4 | ms.date: 1/31/2020 5 | ms.topic: article 6 | keywords: windows 10, uwp, mecm, configmgr, app, msix 7 | ms.custom: RS5 8 | --- 9 | 10 | # Microsoft Endpoint Configuration Manager 11 | The [Microsoft Endpoint Configuration Manager](/configmgr/) can be used to create a `Windows app package (*.appx, *.appxbundle, *.msix, *.msixbundle)` which can be delivered to client devices. Deploying a MSIX app has the following prerequisites: 12 | 1) Access to the MSIX package to deploy. 13 | 2) A device or user collection to be the target of the install. 14 | 15 | ## Deploying MSIX Application 16 | When deploying an Windows app package from within the Microsoft Endpoint Configuration Manager Console to be delivered, you will first require a UNC path to your MSIX app package. The details of the App being created will be retrieved from the meta data contained within the MSIX app package and automatically added into the Windows app package properties. 17 | 18 | | Task | Documentation reference | 19 | |-----|------| 20 | | 1. Capture an MSIX Package from Installer, or retrieve an existing MSIX app | [Create an MSIX Package from desktop installer](../packaging-tool/create-app-package.md) | 21 | | 2. Launch the Microsoft Endpoint Configuration Manager Console | [Microsoft Endpoint Configuration Manager Console](https://devicemanagement.microsoft.com) | 22 | | 3. Create a Line-of Business App | [Create a Windows app package](/configmgr/apps/get-started/creating-windows-applications) | 23 | | 4. Create a user or device collection | [Creating collections](/configmgr/core/clients/manage/collections/create-collections) | 24 | | 5. Deploy the Line-of Business App | [Deploying applications with ConfigMgr](/configmgr/apps/deploy-use/deploy-applications) | 25 | -------------------------------------------------------------------------------- /msix-src/desktop/managing-your-msix-deployment-downgrading.md: -------------------------------------------------------------------------------- 1 | --- 2 | Description: This article provides details on how MSIX applications handle being downgraded. 3 | title: Install earlier versions of an MSIX app package 4 | ms.date: 2/3/2020 5 | ms.topic: article 6 | keywords: windows 10, deployment, msix 7 | ms.assetid: 8 | --- 9 | 10 | # Install earlier versions of an MSIX app package 11 | 12 | Installation of earlier versions of an MSIX app package can be performed on a device without prior removal of the application. Triggering an installation of an earlier version of the same application will cause the client to review the app's manifest file contained within the installing MSIX app package. The review of the appxmanifest.xml file will identify delta differences between the currently installed app and the installer being executed on the device. This process maintains the data stored within the *appdata* folder. Any changes that were made when installing the upgraded version will not be undone if an earlier version of the MSIX app package is installed. 13 | -------------------------------------------------------------------------------- /msix-src/desktop/managing-your-msix-deployment-intune.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: This guide provides instruction on how to create and deploy an MSIX app with Microsoft Intune 3 | title: Microsoft Intune 4 | ms.date: 06/17/2019 5 | ms.topic: article 6 | keywords: windows 10, uwp, mem, mem ac, mem admin console, app, msix 7 | ms.custom: RS5 8 | --- 9 | 10 | # Microsoft Intune 11 | The [Microsoft Intune Console](https://intune.microsoft.com/) can be used to create a Line-of Business App which can be delivered to client devices. When deploying an MSIX app through the Microsoft Intune, you will require an MSIX app to deploy, as well as an Azure Active Directory Group to be the target of the install. 12 | 13 | ## Deploying an MSIX app 14 | When deploying a client app from Microsoft Intune to be delivered to client devices you will first require a local or network path to your MSIX app. The details of the app being created from within the Microsoft Intune will retrieve the meta data contained within the MSIX app package and automatically load the retrieved information into the app properties. 15 | 16 | | Task | Documentation reference | 17 | |-----|------| 18 | | 1. Capture an MSIX Package from Installer, or retrieve an existing MSIX app | [Create an MSIX Package from desktop installer](../packaging-tool/create-app-package.md) | 19 | | 2. Launch the Intune Console | [Microsoft Intune Console](https://portal.azure.com/#blade/Microsoft_Intune_DeviceSettings/ExtensionLandingBlade/overview) | 20 | | 3. Create and deploy a Line-of Business App | [Create a Line-of Business App](/mem/intune/apps/lob-apps-windows) | 21 | -------------------------------------------------------------------------------- /msix-src/desktop/managing-your-msix-deployment-mem-adminconsole.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: This guide provides instruction on how to create and deploy an MSIX app with Microsoft Endpoint Manager Admin Console 3 | title: Microsoft Endpoint Manager Admin Console 4 | ms.date: 06/17/2019 5 | ms.topic: article 6 | keywords: windows 10, uwp, mem, mem ac, mem admin console, app 7 | ms.custom: RS5 8 | --- 9 | 10 | # Microsoft Endpoint Manager Admin Console 11 | The [Microsoft Endpoint Manager Admin Console](https://devicemanagement.microsoft.com) can be used to deploy an MSIX package to client devices. When deploying an MSIX app through the Microsoft Endpoint Configuration Manager admin console, you will require an MSIX app to deploy, as well as an Azure Active Directory Group to be the target of the install. 12 | 13 | ## Deploying MSIX Application 14 | When deploying an App from within the Microsoft Endpoint Manager Admin Console to be delievered, you will first require a local or network path to your MSIX package. The details of the App being created from within the Microsoft Endpoint Manager Admin Console will retrieve the meta data contained within the MSIX app package and automatically load the retrieved information into the App properties. 15 | 16 | | Task | Documentation reference | 17 | |-----|------| 18 | | 1. Capture an MSIX Package from Installer, or retrieve an existing MSIX app | [Create an MSIX Package from desktop installer](../packaging-tool/create-app-package.md) | 19 | | 2. Launch the Microsoft Endpoint Manager Admin Console | [Microsoft Endpoint Manager Admin Console](https://devicemanagement.microsoft.com) | 20 | | 3. Create and deploy a Line-of Business App | [Create a Line-of Business App](/intune/apps/lob-apps-windows) | 21 | -------------------------------------------------------------------------------- /msix-src/desktop/managing-your-msix-deployment-overview.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: This article provides all the details you need to manage deploying you MSIX applications in an enterprise and retail environment. This article is targeted at enterprise and IT Pros. 3 | title: Manage your MSIX deployment Overview 4 | ms.date: 2/3/2020 5 | ms.topic: article 6 | keywords: windows 10, deployment, msix 7 | ms.assetid: 8 | --- 9 | 10 | # Manage your MSIX deployment 11 | 12 | Packaging your application is only half the battle. Next you need to be able to deploy your application to your users. How you deploy your application depends on who your customer is. This section, Managing your MSIX deployment, will discuss deployment of MSIX packages for both enterprise and retail markets. It will provide links and tips and tricks to ensuring a successful experience. 13 | 14 | In order to successfully deploy MSIX, you need to consider the following: 15 | * Who is my customer? 16 | * What dependencies do I have? 17 | * How will I provide the best support for my customer? 18 | 19 | ## Who is my customer? 20 | How you deploy often depends on who is your customer and your role as a developer or administrator. It is important to identify your role to know what tools to use. 21 | 22 | ### IT Pros 23 | IT Pros typically use a software management system to install and manage their apps. In the [Distribute your MSIX in an enterprise environment](managing-your-msix-deployment-enterprise.md) section we will discuss: 24 | * Using Microsoft Endpoint Configuration Manager and Intune to manage your apps 25 | * Using provisioning and DISM to preconfigure machines with MSIX 26 | * Controlling app access with Group Policies and AppLocker 27 | * Distributing apps through the web or Microsoft Store for Business 28 | * Using AppCenter for building, testing, releasing, and desktop apps 29 | 30 | ### Developers 31 | Developers have different tools to distribute their applications. In the [Distribute your MSIX in a retail environment](managing-your-msix-deployment-retail.md) section we will discuss: 32 | * Microsoft Store 33 | * Web Installer 34 | * Using AppCenter for building, testing, releasing, and desktop apps 35 | 36 | ## Dependencies 37 | MSIX is a robust and reliable modern app install experience. The MSIX experience delivers a 99.96% successful install rate. But there are some caveats. MSIX is not supported by default on all versions of Windows, and the supported feature set may very depending on which version of Windows 10 you are deploying to. In the [Plan for your deployment](managing-your-msix-deployment-targetdevices.md) section we will discuss the importance of understanding the target device that the MSIX will be deployed to. 38 | 39 | ## Providing support for my customer 40 | Though MSIX has a 99.96% successful install rate, you still need to plan how to support your customer. In the [MSIX Validation and Troubleshooting section](managing-your-msix-deployment-troubleshooting.md) we discuss tools available for you to diagnose installation issues. 41 | 42 | 43 | 44 | -------------------------------------------------------------------------------- /msix-src/desktop/managing-your-msix-deployment-retail.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: This article provides all the details you need to manage deploying you MSIX applications in an retail environment. This article is targeted at developers. 3 | title: Distribute your MSIX in a consumer environment 4 | ms.date: 2/3/2020 5 | ms.topic: article 6 | keywords: windows 10, deployment, msix 7 | ms.assetid: 8 | --- 9 | 10 | # Distribute your MSIX in a consumer environment 11 | 12 | If you are not an enterprise developer, retail distribution of MSIX can be done through normal retail channels. This includes hosting the MSIX on a web page. 13 | 14 | ## Microsoft Store 15 | 16 | The [Microsoft Store](https://www.microsoft.com/store/apps/windows) can be an excellent way to distribute your application. It has been available to consumers since the launch of Windows 8 in late 2012. Users can browse, search and download apps or games for Windows. 17 | 18 | For details on the Microsoft Store and its capabilities, see [Microsoft Store.](/windows/uwp/publish/) 19 | 20 | To get started on publishing an app to the Microsoft Store and its capabilities, see the [Partner Center](https://partner.microsoft.com/dashboard/home) 21 | 22 | ## App Center 23 | 24 | [App Center](https://appcenter.ms/) enables you to automatically build your app, test it on real devices, and distribute it to beta testers. App Center lets you ship apps more frequently, at higher-quality, and with greater confidence. With App Center you can connect your repo and within minutes automate your builds, test on real devices in the cloud, distribute apps to beta testers, and monitor real-world usage with crash and analytics data. All in one place. 25 | For more information on App Center see [App Center](/appcenter/). 26 | 27 | ## Web Install 28 | 29 | While a MSIX file can be hosted on any IIS server. You can dramatically improve the experience by enabling direct install with App Installer. Direct install will allow the AppInstaller to launch immediately and run the install from the web server rather than downloading it first. For more details on Web install, see 30 | [Installing Windows 10 apps from a web page.](../app-installer/installing-windows10-apps-web.md) 31 | 32 | -------------------------------------------------------------------------------- /msix-src/desktop/managing-your-msix-deployment-troubleshooting.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: This article provides troubleshooting and validation guidance for MSIX installations. 3 | title: Managing your MSIX deployment 4 | ms.date: 2/3/2020 5 | ms.topic: article 6 | keywords: windows 10, deployment, msix 7 | ms.assetid: 8 | --- 9 | 10 | # MSIX validation and troubleshooting 11 | Though MSIX has a 99% successful install rate, sometimes you need to be able to trouble shoot an installation. 12 | 13 | ## Know the application 14 | Understanding the application that you are installing and how it works can go a long way to troubleshooting the user experience. For example, does the application have certain limitations that could be causing the issues? Does the user have access to the resources needed by the application? Were there dependencies the application had, that were not met by the current operating system? 15 | 16 | ## Test your application 17 | Before deploying your application, make sure you have tested your application. The Windows SDK provides a tool, the Windows App Certification Kit that can identify common issues before publication. 18 | To install the latest Windows SDK, [go here.](https://developer.microsoft.com/windows/downloads/windows-10-sdk) 19 | To learn more about the Windows App Certification Kit, see [Windows App Certification Kit](/windows/uwp/debug-test-perf/windows-app-certification-kit) 20 | 21 | ## Flight your application 22 | Another great way to catch issues early is to flight your applications. If you are deploying through the Windows store or Microsoft Store for Business, you can use package flights to deploy your application to a subset of individuals to get additional real world testing. 23 | To learn more about flighting, see [Package flighting.](/windows/uwp/publish/package-flights?context=%252fwindows%252fmsix%252frender) 24 | 25 | ## Device Portal and debugging 26 | Sometimes it is necessary to interact with the application in the user's environment to adequately understand the issue. Windows provides a powerful tool, the [Device Portal Desktop](/windows/uwp/debug-test-perf/device-portal-desktop) which will allow you to connect to the device and interact with the application remotely. 27 | To learn more about Device Portal, see [Device Portal Desktop](/windows/uwp/debug-test-perf/device-portal-desktop). 28 | To learn more about Debugging MSIX packages, see [Run, debug, and test a packaged desktop application.](./desktop-to-uwp-debug.md) 29 | 30 | ## Installation issues 31 | When there are issues with the installation, you can investigate the artifacts provided by AppInstaller. First, AppInstaller provides error code failures. If the error code for any failure is not sufficient to determine what is wrong, the AppInstaller also logs all interactions to the Event Viewer. You will find the logs here: Application and Services Logs->Microsoft->Windows->AppxDeployment-Server. 32 | 33 | You can use the Event Viewer or PowerShell to access those events. 34 | To learn more about how to view the events, see [Troubleshooting packaging, deployment, and query of Windows apps.](/windows/win32/appxpkg/troubleshooting) 35 | 36 | To learn more about AppInstaller troubleshooting, see [Troubleshoot Appinstaller Issues.](../app-installer/troubleshoot-appinstaller-issues.md) 37 | 38 | 39 | ## Next steps 40 | 41 | Have questions? Ask us on Stack Overflow. Our team monitors these [tags](https://stackoverflow.com/questions/tagged/project-centennial+or+desktop-bridge). 42 | 43 | -------------------------------------------------------------------------------- /msix-src/desktop/managing-your-msix-reset-and-repair.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: This article provides details regarding the the reset and repair of MSIX apps that have been deployed to a device. 3 | title: Reset or Repair MSIX Apps 4 | ms.date: 11/10/2020 5 | ms.topic: article 6 | keywords: windows 10, deployment, msix, reset, repair 7 | ms.assetid: 8 | --- 9 | 10 | # Reset or Repair MSIX apps 11 | 12 | ## Overview 13 | 14 | Windows apps (*.msix, *.msixbundle, *.appx, and *.appxbundle) offer functionality known as App Reset, and Repair. Which can be performed by the device user (without elevation) to re-install or refresh the Windows app installation in an attempt to resolve a failure with a Windows app. 15 | 16 | ## Repair 17 | 18 | You can repair Windows apps that have been installed to an online Windows image. When you use the Windows Settings to repair a Windows app, it will retain the app's data, as it attempts to re-load the application. 19 | 20 | ### Repairing a Windows app 21 | 22 | Repairing a Windows app using the Windows Settings: 23 | 1. Open the Settings app from the Start Menu. 24 | 1. Select the **Apps** menu item. 25 | 1. Select the **Apps & Features** menu item, from the left side navigation. 26 | 1. Select the app that needs to be reset. 27 | 1. Select the **Advanced options** link. 28 | 1. Select the **Repair** button. 29 | 30 | 31 | ## Reset 32 | 33 | You can reset Windows apps that have been installed to an online Windows image. When you use the PowerShell cmdlets, or the Windows Settings app to reset a Windows app, it will permanently delete the app's data, and re-install the app fresh. The Windows app will lose preferences, and/or sign-in details, etc. 34 | 35 | ### Resetting a Windows app 36 | 37 | Resetting a Windows app using Windows PowerShell: 38 | 1. Open an administrative PowerShell window, and type: 39 | ```PowerShell 40 | Get-AppxPackage -Name "MyEmployees" | Reset-AppxPackage 41 | ``` 42 | 43 | Resetting a Windows App using the Windows Settings: 44 | 1. Open the Settings app from the Start Menu. 45 | 1. Select the **Apps** menu item. 46 | 1. Select the **Apps & Features** menu item, from the left side navigation. 47 | 1. Select the App that needs to be reset. 48 | 1. Select the **Advanced options** link. 49 | 1. Select the **Reset** button. 50 | 1. In the confirmation prompt, select the **Reset** button. 51 | -------------------------------------------------------------------------------- /msix-src/desktop/media/app-attach-from-visualstudio/image.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/media/app-attach-from-visualstudio/image.png -------------------------------------------------------------------------------- /msix-src/desktop/media/app-attach-from-visualstudio/image1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/media/app-attach-from-visualstudio/image1.png -------------------------------------------------------------------------------- /msix-src/desktop/media/app-attach-from-visualstudio/screenshot-2023-05-30-165600.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/media/app-attach-from-visualstudio/screenshot-2023-05-30-165600.png -------------------------------------------------------------------------------- /msix-src/desktop/media/app-attach-from-visualstudio/screenshot-2023-05-30-165836.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/media/app-attach-from-visualstudio/screenshot-2023-05-30-165836.png -------------------------------------------------------------------------------- /msix-src/desktop/media/app-attach-from-visualstudio/screenshot-2023-10-11-180059.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/media/app-attach-from-visualstudio/screenshot-2023-10-11-180059.png -------------------------------------------------------------------------------- /msix-src/desktop/media/app-attach-from-visualstudio/screenshot-2023-10-11-181102.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/media/app-attach-from-visualstudio/screenshot-2023-10-11-181102.png -------------------------------------------------------------------------------- /msix-src/desktop/media/app-attach-from-visualstudio/screenshot-2023-10-11-182632.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/media/app-attach-from-visualstudio/screenshot-2023-10-11-182632.png -------------------------------------------------------------------------------- /msix-src/desktop/media/desktop-to-uwp-packaging-dot-net/microsoftteams-image-(12).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/media/desktop-to-uwp-packaging-dot-net/microsoftteams-image-(12).png -------------------------------------------------------------------------------- /msix-src/desktop/media/msix-packaging-extension/ado-extension-image1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/media/msix-packaging-extension/ado-extension-image1.png -------------------------------------------------------------------------------- /msix-src/desktop/media/msix-packaging-extension/ado-extension-image2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/media/msix-packaging-extension/ado-extension-image2.png -------------------------------------------------------------------------------- /msix-src/desktop/media/msix-packaging-extension/ado-extension-image3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/desktop/media/msix-packaging-extension/ado-extension-image3.png -------------------------------------------------------------------------------- /msix-src/desktop/register-from-network.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: This article provides guidance on how to register a package layout from a network share 3 | title: Registering a package layout from a network share 4 | ms.date: 02/06/2020 5 | ms.topic: article 6 | keywords: windows 10, uwp, msix 7 | ms.assetid: f45d8b14-02d1-42e1-98df-6c03ce397fd3 8 | --- 9 | 10 | # Registering a package layout from a network share 11 | 12 | Collaborative and multi-device development can be time consuming due to the need to copy packages, repositories, build folders etc. If you're developing on Windows 10 version 1709 and later you can take advantage of a feature to build your package layout to a network share and then register the layout on a remote device directly from the network. 13 | 14 | Multiple people can contribute to a single app package layout on a network share and changes will be visible to other collaborators and users who registered the app. If you are building an app for multiple devices you can take advantage of the feature and avoid having to copy the app to each device for testing. 15 | 16 | ## Prerequisites 17 | 18 | 1. Your devices must be on Windows 10 Creators Update Insider Build 14965 or later. 19 | 20 | 2. You will need to enable developer mode and device discovery on all devices. 21 | 22 | 3. Collaborators will need read and write access to the build folder. 23 | 24 | 4. Users will only need to read access to the build folder. 25 | 26 | ## In Visual Studio 27 | 28 | If you are developing in Visual Studio you can follow the steps outlined [here](/windows/uwp/debug-test-perf/deploying-and-debugging-uwp-apps#advanced-remote-deployment-options). 29 | 30 | ## From the command line 31 | 32 | If you are not developing in Visual Studio, and using command line tools you can use [WinAppDeployCmd](/windows/uwp/packaging/install-universal-windows-apps-with-the-winappdeploycmd-tool). Below is an example of how to do so from a command line window: 33 | 34 | ``` 35 | WinAppDeployCmd.exe registerfiles -remotedeploydir -ip -pin 36 | ``` 37 | - Network Path – Path to the app’s loose files 38 | 39 | - P Address – enter the IP Address of the target machine here 40 | 41 | - Pin - A pin if it is required to establish a connection with the target device. (You will be prompted to retry with the -pin option if authentication is required.) Click here to learn how to get a PIN. 42 | 43 | 44 | You can also build a fully packaged application that accesses files in a network share during testing and validation. See this sample for an [example](https://github.com/AppInstaller/Windows-appsample-marble-maze). 45 | -------------------------------------------------------------------------------- /msix-src/desktop/tamper-protection.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: Enforce a packag integrity check at run time 3 | title: Enforce Package Integrity Check 4 | author: andreww-msft 5 | ms.date: 03/25/2021 6 | ms.topic: article 7 | keywords: windows 10, uwp 8 | --- 9 | 10 | # Enforce Package Integrity Check 11 | Windows is able to run time package integrity checks on the entire contents of the package. If enabled, Windows will perform run time checks and initiate a package remediation and repair workflow before launching the app if it detects a tampered or corrupt package. 12 | 13 | ## How to enable this 14 | In the package manifest , insert the following element: 15 | 16 | ```xml 17 | 18 | 19 | 20 | 21 | 22 | 23 | ``` 24 | 25 | By checking indicating that **Enforcement** is **on**, this will indicate that Windows will enforce run time package integrity checks on the entire contents of the package. There are three values that **Enforcement** can be, **on**, **off** or **default**. The value **default** is the same behavior as **off** 26 | 27 | ## User experience 28 | When package integrity is checked and the system identifies that the package files have been tampered with, depending on the source of the package, a dialog will appear to the user indicating that there is an issue with the app. If the app comes from the store, the user will be directed to act via the Store app. If the app comes from outside the Microsoft Store, the user dialog will be generic. The user will be prompted to go to the Settings app and either **Repair** or **Reset** the app. 29 | -------------------------------------------------------------------------------- /msix-src/desktop/validation-overview.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: This section provides information on validating, testing, and troubleshooting MSIX packages. This section is targeted at enterprise and IT Pros. 3 | title: MSIX validation, testing and troubleshooting 4 | ms.date: 2/3/2020 5 | ms.topic: article 6 | keywords: windows 10, deployment, msix 7 | ms.assetid: 8 | --- 9 | 10 | # MSIX validation, testing and troubleshooting 11 | 12 | This section provides information on validating, testing, and troubleshooting MSIX packages. 13 | 14 | | Article | Description | 15 | |---------|-------------| 16 | | [Troubleshooting packaging, deployment, and query of Windows apps](/windows/win32/appxpkg/troubleshooting?context=%2Fwindows%2Fmsix%2Frender) | Use these suggestions to troubleshoot problems you experience when packaging, deploying, or querying a Windows app package (.msix/.appx) as a developer. | 17 | | [Troubleshoot runtime issues in an MSIX container](../manage/troubleshoot-msix-container.md) | Review how you can troubleshoot runtime issues occurring in a MSIX container. | 18 | | [MSIX support on Windows Server 2019](../msix-server-2019.md) | Details about support for MSIX on Windows Server 2019 | 19 | | [Windows Device Portal overview](/windows/uwp/debug-test-perf/device-portal?context=%2Fwindows%2Fmsix%2Frender) | The Windows Device Portal (WDP) is a web server included with Windows devices that lets you configure and manage the settings for the device over a network or USB connection (local connections are also supported on devices with a web browser). | 20 | | [Run, debug, and test an MSIX package](desktop-to-uwp-debug.md) | Shows you how to run your packaged application and see how it looks without having to sign it, set breakpoints and step through code, test your application in a production environment, sign your application, and then install it. | 21 | | [Detect package identity and runtime context](../detect-package-identity.md) | Detect whether your app was deployed as an MSIX package by using the Windows Package Manager API, or your own custom installer. | 22 | | [Registering a package layout from a network share](register-from-network.md) | Build your package layout to a network share and then register the layout on a remote device directly from the network. | 23 | | [Test your Windows app for Windows 10 in S mode](desktop-to-uwp-test-windows-s.md) | Test your Windows app to ensure that it will operate correctly on devices that run Windows 10 in S mode. | 24 | | [Known Issues with packaged desktop apps](desktop-to-uwp-known-issues.md) | This article contains known issues that can occur when you create an MSIX package for your desktop app. | -------------------------------------------------------------------------------- /msix-src/desktop/vs-package-overview.md: -------------------------------------------------------------------------------- 1 | --- 2 | Description: Visual Studio makes it easy to generate MSIX packages and is the recommended approach for applications in development. 3 | title: Package your app as an MSIX in Visual Studio 4 | ms.date: 01/27/2020 5 | ms.topic: article 6 | keywords: windows 10, uwp 7 | ms.custom: RS5 8 | --- 9 | 10 | # Package your app as an MSIX in Visual Studio 11 | 12 | Visual Studio makes it easy to generate MSIX packages and is the recommended tool for packaging applications in development. Desktop apps (Windows Forms, WPF, Win32 etc.) can use the Windows Application Packaging Project to generate an MSIX package. Universal Windows Platform (UWP) apps have the ability to generate MSIX packages built into their default project type. To generate an MSIX package for a desktop application, you first need to add the Windows Application Packaging Project to your solution. This step is not required for UWP apps. 13 | 14 | |Topic| Description | 15 | |:---|:---| 16 | |[Setup your desktop app for packaging in Visual Studio](desktop-to-uwp-packaging-dot-net.md)| This section discusses how to setup your desktop application (Winforms, WPF, Win32 etc.) for packaging using the Windows Application Packaging Project in Visual Studio. | 17 | |[Packaging a desktop or UWP app in Visual Studio](../package/packaging-uwp-apps.md)| This section discusses how to generate MSIX packages for your desktop or UWP apps in Visual Studio.| 18 | |[Extending your packaged application](extend-overview.md)| This section discusses how to extend your application using extensions and optional packages.| 19 | -------------------------------------------------------------------------------- /msix-src/docfx.json: -------------------------------------------------------------------------------- 1 | { 2 | "build": { 3 | "content": [ 4 | { 5 | "files": [ 6 | "**/*.md", 7 | "**/*.yml" 8 | ], 9 | "exclude": [ 10 | "**/obj/**", 11 | "**/includes/**", 12 | "_themes/**", 13 | "_themes.pdf/**", 14 | "README.md", 15 | "LICENSE", 16 | "LICENSE-CODE", 17 | "ThirdPartyNotices" 18 | ] 19 | } 20 | ], 21 | "resource": [ 22 | { 23 | "files": [ 24 | "**/*.png", 25 | "**/*.jpg" 26 | ], 27 | "exclude": [ 28 | "**/obj/**", 29 | "**/includes/**", 30 | "_themes/**", 31 | "_themes.pdf/**" 32 | ] 33 | } 34 | ], 35 | "overwrite": [], 36 | "externalReference": [], 37 | "globalMetadata": { 38 | "ms.subservice": "msix", 39 | "breadcrumb_path": "/windows/msix/breadcrumb/toc.json", 40 | "uhfHeaderId": "MSDocsHeader-MSIX", 41 | "titleSuffix": "MSIX", 42 | "feedback_system": "Standard", 43 | "feedback_product_url": "https://aka.ms/msixcommunity", 44 | "feedback_help_link_url": "https://learn.microsoft.com/answers/tags/184/windows-app-sdk/", 45 | "feedback_help_link_type": "get-help-at-qna", 46 | "ms.service": "windows", 47 | "searchScope": ["MSIX"] 48 | }, 49 | "fileMetadata": { 50 | "ms.author": 51 | { 52 | "app-package-updates.md": "larryhu", 53 | "customer-journey.md": "larryhu", 54 | "detect-package-identity.md": "larryhu", 55 | "group-policy-msix.md": "larryhu", 56 | "index.yml": "larryhu", 57 | "modification-packages.md": "larryhu", 58 | "msix-container.md": "larryhu", 59 | "msix-server-2019.md": "larryhu", 60 | "non-store-developer-updates.md": "larryhu", 61 | "overview.md": "larryhu", 62 | "partners.md": "larryhu", 63 | "resources.md": "larryhu", 64 | "store-developer-package-update.md": "larryhu", 65 | "supported-platforms.md": "larryhu", 66 | "app-installer/**.md": "larryhu", 67 | "customer/**.md": "larryhu", 68 | "desktop/**.md": "larryhu", 69 | "manage/**.md": "larryhu", 70 | "msix-sdk/**.md": "larryhu", 71 | "msix-core/**.md": "larryhu", 72 | "package/**.md": "larryhu", 73 | "packaging-tool/**.md": "larryhu", 74 | "toolkit/**.md": "kevinla", 75 | "psf/**.md": "larryhu" 76 | }, 77 | "author": 78 | { 79 | "app-package-updates.md": "larhu", 80 | "customer-journey.md": "larhu", 81 | "detect-package-identity.md": "larhu", 82 | "group-policy-msix.md": "larhu", 83 | "index.yml": "larhu", 84 | "modification-packages.md": "larhu", 85 | "msix-container.md": "larhu", 86 | "msix-server-2019.md": "larhu", 87 | "non-store-developer-updates.md": "larhu", 88 | "overview.md": "larhu", 89 | "partners.md": "larhu", 90 | "resources.md": "larhu", 91 | "store-developer-package-update.md": "larhu", 92 | "supported-platforms.md": "larhu", 93 | "app-installer/**.md": "larhu", 94 | "customer/**.md": "larhu", 95 | "desktop/**.md": "larhu", 96 | "manage/**.md": "larhu", 97 | "msix-sdk/**.md": "larhu", 98 | "msix-core/**.md": "larhu", 99 | "package/**.md": "larhu", 100 | "packaging-tool/**.md": "larhu", 101 | "toolkit/**.md": "KevinLaMS", 102 | "psf/**.md": "larhu" 103 | } 104 | }, 105 | "template": [], 106 | "dest": "msix", 107 | "markdownEngineName": "markdig" 108 | } 109 | } 110 | -------------------------------------------------------------------------------- /msix-src/images/AccessITAutomationLogoTransp.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/AccessITAutomationLogoTransp.png -------------------------------------------------------------------------------- /msix-src/images/AccessItItAutomationLogoRebranded.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/AccessItItAutomationLogoRebranded.png -------------------------------------------------------------------------------- /msix-src/images/AdvancedInstaller_Logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/AdvancedInstaller_Logo.png -------------------------------------------------------------------------------- /msix-src/images/AppCure-WB-fixed.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/AppCure-WB-fixed.png -------------------------------------------------------------------------------- /msix-src/images/AppCure-WB.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/AppCure-WB.png -------------------------------------------------------------------------------- /msix-src/images/Apptimized_Logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/Apptimized_Logo.png -------------------------------------------------------------------------------- /msix-src/images/Camwood_Logo.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/Camwood_Logo.jpg -------------------------------------------------------------------------------- /msix-src/images/Camwood_Logo_2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/Camwood_Logo_2.png -------------------------------------------------------------------------------- /msix-src/images/CloudHouse_Logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/CloudHouse_Logo.png -------------------------------------------------------------------------------- /msix-src/images/DB_logo_red_outlined_200px_rgb.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/DB_logo_red_outlined_200px_rgb.png -------------------------------------------------------------------------------- /msix-src/images/ECNO_masterlogo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/ECNO_masterlogo.png -------------------------------------------------------------------------------- /msix-src/images/EMCO_Software_Logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/EMCO_Software_Logo.png -------------------------------------------------------------------------------- /msix-src/images/FireGiant_Logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/FireGiant_Logo.png -------------------------------------------------------------------------------- /msix-src/images/Flexera_Logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/Flexera_Logo.png -------------------------------------------------------------------------------- /msix-src/images/InfoPulse_Logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/InfoPulse_Logo.png -------------------------------------------------------------------------------- /msix-src/images/Logo-MIDGmbH.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/Logo-MIDGmbH.png -------------------------------------------------------------------------------- /msix-src/images/Logo_SE_Green_RGB-Screen.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/Logo_SE_Green_RGB-Screen.png -------------------------------------------------------------------------------- /msix-src/images/MPT-mod-page.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/MPT-mod-page.png -------------------------------------------------------------------------------- /msix-src/images/MP_logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/MP_logo.png -------------------------------------------------------------------------------- /msix-src/images/PACE-Suite-white-for-dark-background-small.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/PACE-Suite-white-for-dark-background-small.png -------------------------------------------------------------------------------- /msix-src/images/PACE-suite-logos.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/PACE-suite-logos.png -------------------------------------------------------------------------------- /msix-src/images/Pace_Logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/Pace_Logo.png -------------------------------------------------------------------------------- /msix-src/images/RayPackStudio_Logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/RayPackStudio_Logo.png -------------------------------------------------------------------------------- /msix-src/images/RayPackStudio_Logo_offset.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/RayPackStudio_Logo_offset.png -------------------------------------------------------------------------------- /msix-src/images/Raynet_Logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/Raynet_Logo.png -------------------------------------------------------------------------------- /msix-src/images/Revenera_light.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/Revenera_light.png -------------------------------------------------------------------------------- /msix-src/images/Rimo3_Logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/Rimo3_Logo.png -------------------------------------------------------------------------------- /msix-src/images/SAP_R_grad.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/SAP_R_grad.png -------------------------------------------------------------------------------- /msix-src/images/SSH2_Logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/SSH2_Logo.png -------------------------------------------------------------------------------- /msix-src/images/Trend_Micro-lightmode.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/Trend_Micro-lightmode.png -------------------------------------------------------------------------------- /msix-src/images/installAware_logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/installAware_logo.png -------------------------------------------------------------------------------- /msix-src/images/liquit_logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/liquit_logo.png -------------------------------------------------------------------------------- /msix-src/images/msix-bad-cert.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/msix-bad-cert.png -------------------------------------------------------------------------------- /msix-src/images/msix-good-cert.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/msix-good-cert.png -------------------------------------------------------------------------------- /msix-src/images/readiness-logo-offset.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/readiness-logo-offset.png -------------------------------------------------------------------------------- /msix-src/images/readiness-logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/readiness-logo.png -------------------------------------------------------------------------------- /msix-src/images/start-comp-cert.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/images/start-comp-cert.png -------------------------------------------------------------------------------- /msix-src/manage/create-directory.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: This is guide the declare a directory in any location based on package app directory in the Manifest. 3 | title: Create a directory in any location based on packaged app directory 4 | ms.date: 11/04/2021 5 | ms.topic: article 6 | keywords: msix 7 | --- 8 | 9 | # Create a directory in any location based on packaged app directory 10 | In order to satisfy certain requirements, apps may require the files to appear in their existing install directory. For example, if a particular app was expecting a file in a folder, like C:\Program Files\Contoso; that directory can be modified by the admins. Starting in Windows 11, apps can specify a directory outside of the WindowsApps directory and the OS will ensure that files will appear in that location with proper ACLs inherited from the parent directory. 11 | 12 | ## Declaring the location of the directory in the manifest 13 | To enable this feature, the package will need to declare where to project the files in the package to. Below is an example 14 | 15 | ```xml 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | ``` 26 | ## Considerations for projection 27 | Before using this feature, here are a list of considerations: 28 | 29 | |Considerations | Description | 30 | |----------|-----------| 31 | |How to install a package with the ability to project? |Packages have to install through ProvisionPackageForAllUsers API | 32 | |Who can install it (users or admins)? |Admin | 33 | |Where can the files be projected to (locked location, or anywhere at all)?|Anywhere besides %pf%\windowsapps or %pf%\modifiablewindowsapps | 34 | |What are the ACLs on the projected directory if we create it?|Inherited from parent directory | 35 | |Can more than one package declare the same directory?|We do not allow more than one related set to declare the same directory. In other words, if there are multiple packages declaring the same directory, they must all be from the same related set. | 36 | |What about more than one publisher?|No | 37 | |How are collisions handled?|Packages and/or pre-existing files are merged. Conflicting files are resolved in specified priority order, or package-name alphabetically, if no order specified | 38 | 39 | 40 | 41 | -------------------------------------------------------------------------------- /msix-src/manage/troubleshoot-msix-container.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: Learn about the tools used to diagnose and troubleshoot runtime issues that can occur in an MSIX container. 3 | title: Troubleshoot runtime issues in an MSIX container 4 | ms.date: 07/11/2019 5 | ms.topic: article 6 | keywords: windows 10, uwp, msix 7 | ms.assetid: 807a99a7-d285-46e7-af6a-7214da908907 8 | --- 9 | 10 | # Troubleshoot runtime issues in an MSIX container 11 | 12 | In this article, we will review how you can troubleshoot runtime issues occurring in a MSIX container. MSIX containers by themselves are relatively simple and straightforward. As more applications are run inside the same package identity with the help of modification packages, the virtual registry and virtual file system will be over-layed in the order in which the applications are installed. 13 | 14 | There can be cases where the order in which these applications are installed could cause unforseen issues where the expected registry keys might be overwritten and expected files might be replaced. 15 | 16 | To assist in diagnosing such issues, [Invoke-CommandInDesktopPackage](/powershell/module/appx/invoke-commandindesktoppackage&preserve-view=true) is a PowerShell cmdlet that can be used to run an application inside the MSIX container. This allows for users to run command prompt, registry editor, PowerShell inside the MSIX container and get a view of the merged file system and merged registry hive. 17 | 18 | > [!IMPORTANT] 19 | > Invoke-CommandInDesktopPackage requires the device to be in Developer mode for Windows 10 builds prior to 18922. 20 | 21 | 22 | ## View the merged file system 23 | 24 | To view the file system as observed by the applications that are running inside the container, use the following PowerShell command: 25 | 26 | ``` PowerShell 27 | Invoke-CommandInDesktopPackage -AppId "AppPackage1" -PackageFamilyName "Contoso.AppPackage1_8h66172c634n0" -Command "cmd.exe" -PreventBreakaway 28 | ``` 29 | 30 | The above command will launch an instance of cmd.exe in the *Contoso.AppPackage1_8h66172c634n0* package container. As you are running the command prompt from inside the container, you can browse through the file system and view the merged files. 31 | 32 | ## View the merged registry hive 33 | 34 | To view the full device registry hive as observed by the applications that are running insider the container, use the following PowerShell command: 35 | 36 | ``` PowerShell 37 | Invoke-CommandInDesktopPackage -AppId "AppPackage1" -PackageFamilyName "Contoso.AppPackage1_8h66172c634n0" -Command "regedit.exe" -PreventBreakaway 38 | ``` 39 | 40 | The above command will launch registry editor within the context of the *Contoso.AppPackage1_8h66172c634n0* package container. Here you can browse through local machine and current user registry keys and identify possible offender that is causing the issue. 41 | 42 | >[!TIP] 43 | > Use '-PreventBreakaway' flag while using Invoke-CommandInDesktopPackage if you would like to launch subsequent processes in the same container. Else, any subsequent launch will break out of the container. 44 | 45 | >[!NOTE] 46 | > Not all applications can be launched within the container. For instance, explorer.exe will breakout of the container. 47 | -------------------------------------------------------------------------------- /msix-src/media/partners/app-v-scheduler-logo2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/media/partners/app-v-scheduler-logo2.png -------------------------------------------------------------------------------- /msix-src/msix-core/deploy-with-msix-core.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Deploy an MSIX package with MSIX Core 3 | description: Describes how to deploy an MSIX package with MSIX Core by using the msixmgr.exe tool. 4 | ms.date: 12/19/2019 5 | ms.topic: article 6 | keywords: windows 10, windows 7, windows 8, Windows Server, uwp, msix, msixcore, 1709, 1703, 1607, 1511, 1507 7 | ms.custom: "RS5, seodec18" 8 | --- 9 | 10 | # Deploy an MSIX package with MSIX Core 11 | 12 | [MSIX Core](msixcore.md) brings MSIX deployment to select previous versions of Windows. To get started, first make sure that MSIX Core is installed on target device. 13 | 14 | ## MSI installation 15 | 16 | We recommend using our provided MSI installers to install MSIX Core because they automatically add msixmgr.exe to your search path and associate the MSIX extension with the installer. 17 | 18 | You can download the following architecture-specific MSI installers from the **Assets** section on our [release page](https://github.com/microsoft/msix-packaging/releases): 19 | 20 | * **msixmgrSetup-x64.msi** 21 | * **msixmgrSetup-86.msi** 22 | 23 | > [!NOTE] 24 | > Make sure you choose the correct installer for your device's architecture. This will impact where the installer will store important files. The name of the file may change based on the version of the installer. 25 | 26 | ## Installing your certificate 27 | 28 | MSIX packages are required to be signed. Before installing any MSIX packages, make sure you have installed the certificate you used to sign your packages. You can do this using you normal workflows for installing certificate from your management tool. 29 | 30 | If you want to manually install a certificate you can run this command from an elevated command prompt: 31 | 32 | ```PowerShell 33 | certutil -addstore root 34 | ``` 35 | 36 | > [!NOTE] 37 | > You should add your trusted certificate under Trusted Root Certification Authority in all scenarios. 38 | 39 | ## Using the Command Line 40 | 41 | Once the tool msixmgr.exe is installed, it can be used to manage your MSIX packages on this machine by searching, installing, and removing. The command line utility msixmgr.exe is intended for system administrators. It is most useful when run from administrator prompt. Not all commands when run from a regular command prompt will display to the console. See below for more details. 42 | 43 | ### Install 44 | 45 | Using command prompt or PowerShell, navigate to the directory that contains msixmgr.exe and run the following command to install your MSIX package. The `-quietUX` parameter can also be added at the end of the command so that users don't see the installer UI. 46 | 47 | ```PowerShell 48 | msixmgr.exe -AddPackage C:\NotePadPlus\notepadplus.msix -quietUX 49 | ``` 50 | 51 | > [!NOTE] 52 | > This and the following examples use **notepadplus.msix**. This is one of our [sample packages](https://github.com/microsoft/msix-packaging/tree/master/MsixCore/Tests). 53 | 54 | ### Querying for a specific MSIX Package 55 | 56 | Searching for a specific package is possible by **packageFullName**, **packageFamilyName** and/or using wildcards as well. Supported wildcards are *(match any character) and ?(match single character). 57 | 58 | ```PowerShell 59 | msixmgr.exe -FindPackage notepadplus_0.0.0.1_???__8wekyb3d8bbwe 60 | msixmgr.exe -FindPackage *padplus_0.0.* 61 | msixmgr.exe -FindPackage *epadplus_8wekyb3d8bbw? 62 | ``` 63 | 64 | ### Uninstall 65 | 66 | To uninstall use the following command: 67 | 68 | ```PowerShell 69 | msixmgr.exe -RemovePackage notepadplus_0.0.0.1_x64__8wekyb3d8bbwe -quietUX 70 | ``` 71 | -------------------------------------------------------------------------------- /msix-src/msix-core/msixcore.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: MSIX Core 3 | description: Learn about how to set up MSIX Core to create an MSIX installation package of MSIX apps for installing on previous versions of Windows. 4 | ms.date: 12/19/2019 5 | ms.topic: article 6 | keywords: windows 10, windows 7, windows 8, Windows Server, uwp, msix, msixcore, 1709, 1703, 1607, 1511, 1507 7 | ms.custom: "RS5, seodec18" 8 | --- 9 | 10 | # MSIX Core 11 | 12 | MSIX Core brings MSIX support to versions of Windows earlier than Windows 10, version 1709. MSIX Core is an [open source project](https://github.com/Microsoft/msix-packaging/tree/master/MsixCore) on GitHub that enables these earlier Windows versions to install MSIX packages. You can start by downloading the [latest release](https://github.com/microsoft/msix-packaging/releases/tag/MSIX-Core-1.1-release) or the [preview builds](https://github.com/microsoft/msix-packaging/releases/tag/MSIX-Core-preview). 13 | 14 | With MSIX Core, developers and IT pros who need to support users on these earlier Windows versions can now adopt and take advantage of the benefits of MSIX. 15 | 16 | ## What is MSIX Core? 17 | 18 | MSIX Core enables the installation of MSIX apps on previous versions of Windows, provided that the apps are already built to work on those versions of Windows. MSIX Core is built for the following Windows versions that don't currently natively support MSIX: 19 | 20 | * Windows 7 SP1 21 | * Windows 8.1 22 | * Currently supported Windows Server (with Desktop Experience) 23 | * Windows 10 versions prior to 1709 24 | 25 | MSIX Core is designed for both developers and IT pros. Developers can use the MSIX Core Library to enable their existing installers to install their packaged apps on previous Windows versions, so they can produce just one MSIX package to target all Windows users. IT pros can download the MSIX Core Installer. MSIX Core installer enables command line installation of MSIX along with the ability for users to install MSIX packages simply by double clicking them. 26 | 27 | ## Considerations of MSIX Core 28 | 29 | The goal of MSIX Core is to enable the install, query, and removal of packaged apps (that already work on those Windows versions), and provide as clean of an uninstall as possible. MSIX Core provides a subset of features of native MSIX, functioning similar to existing Win32 installer types. 30 | 31 | * MSIX Core does not provide the container benefits of native MSIX, nor enable an app that uses Windows 10 specific features to work on previous Windows versions. 32 | * When using MSIX Core on a down-level OS, [app execution aliases](/windows/apps/desktop/modernize/desktop-to-uwp-extensions#start-your-application-by-using-an-alias) will only work from **Win+R** and not from Command Prompt or PowerShell. 33 | * MSIX Core does not support Microsoft Store integration. Developers who want to publish their applications to the Store can follow the documentation [here](/windows/uwp/publish/). 34 | 35 | ## Get started 36 | 37 | To deploy your MSIX package with MSIX Core, you must first [update your existing MSIX manifest](support-msix-core.md). Then, you can [deploy your MSIX package with MSIX Core](deploy-with-msix-core.md) (if you only have the package) or you can [create an MSIX package with MSIX Core from source code](msixcore-clickonce-solution.md) (if you have the source code). 38 | -------------------------------------------------------------------------------- /msix-src/msix-sdk/msix-linux.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: How to build MSIX package on Linux  3 | description: This article gives an overview of how to create an MSIX package on a Linux machine using the MSIX SDK 4 | ms.date: 08/16/2022 5 | ms.topic: article 6 | keywords: windows 10, windows 11, linux, uwp, msix 7 | ms.custom: RS5 8 | --- 9 | 10 | # How to build MSIX package on Linux 11 | The MSIX SDK project includes cross-platform API support for packing and unpacking .msix/.appx packages. The project includes a shared library (.so file) that enables MSIX packages to be packaged on Linux. This library exports a subset of the functionality contained within appxpackaging.dll on Windows. 12 | 13 | To learn more about creating, reading and writing an app package, visit the [Packaging API](/windows/win32/appxpkg/interfaces) page. 14 | 15 | ## Build the MSIX package 16 | On a Linux machine use the following commands to build an MSIX package: 17 | 18 | ``` 19 |    ./makelinux [options] 20 |    ./makeaosp [options] 21 | ``` 22 | 23 | ## Use the MSIX package 24 | 25 | After creating your MSIX package on Linux, you have a few options: 26 | 27 | * Distribute your app on the Microsoft Store for business. There is no need to sign it yourself in this case. 28 | 29 | * Use this Azure Dev Ops [MSIX Packaging Extension](https://marketplace.visualstudio.com/items?itemName=MSIX.msix-ci-automation-task) to help sign your package in a Windows agent. A sample pipeline can be [found here](https://github.com/microsoft/msix-packaging/blob/master/tools/pipelines-tasks/azure-pipelines/sample-pipeline.yml). 30 | 31 | * Generate the MSIX package on Linux and copy it over to a Windows machine to sign it by using [signtool](/windows/msix/package/sign-app-package-using-signtool). 32 | -------------------------------------------------------------------------------- /msix-src/msix-sdk/release-notes/sdk-release-notes-1.4.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: MSIX SDK Release 1.4 release notes 3 | description: This article provides release notes for version 1.4 of the MSIX SDK. This SDK is available on GitHub. 4 | ms.date: 09/12/2018 5 | ms.topic: article 6 | keywords: windows 10, uwp, msix 7 | ms.custom: RS5 8 | --- 9 | 10 | # MSIX SDK 1.4 update 11 | 12 | With the SDK release (1.4), we are continuing to add more functionality and make performance improvements to our SDK. With the release of 1.4, developers can use the SDK to now unpack and extract app bundles and [flat bundles](../../package/flat-bundles.md). 13 | 14 | With the support of bundles, client apps can now extract app bundles and only download and extract the packages inside the bundle that are applicable. In this release, the bundle support extends to flat bundles as well. This means that the client app that consuming the bundle can access the bundle manifest and specify the app packages that it wants to extract - leaving the choice and control to the developer. The SDK calls the native OS for language and locale information and provides that info to the client app which it can use to make the choice of appropriate package from the bundle as well. 15 | 16 | With the new SDK, we added support for MSXML6 for Windows which removes the out of box dependency and thus reduces the size of the binary and use the native XML library. 17 | 18 | Along with removing dependency in Windows, we also removed the dependency on zlib (3rd party library) and use in-box implementations on MacOS, iOS and Android(AOSP). Additionally, we made other improvements to reduce the binary size on all platforms. 19 | 20 | Along with the performance and feature improvements, we are also including better samples that developers can use to get started with the SDK. Using the samples, developers can learn how to implement some of the public interfaces required to read the msix packages. 21 | 22 | You can get the latest SDK on GitHub. 23 | 24 |

MSIX SDK on GitHub

25 | 26 | -------------------------------------------------------------------------------- /msix-src/msix-sdk/release-notes/sdk-release-notes-1.5.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: MSIX SDK Version 1.5 release notes 3 | description: This article provides release notes for version 1.5 of the MSIX SDK. This SDK is available on GitHub. 4 | ms.date: 02/06/2018 5 | ms.topic: article 6 | keywords: windows 10, uwp, msix 7 | ms.custom: 19H1 8 | --- 9 | 10 | # MSIX SDK 1.5 update 11 | 12 | With the SDK release (1.5), our main investment was in reducing the binary size of the SDK. One of the key feedback about our SDK was the size and especially for mobile apps having a binary dependency that is going to cost ~5MB isn't satisfactory. 13 | 14 | To resolve this, we replaced the static binary dependencies for XML parsing with inbox binaries on Android and iOS/MacOS. As part of the binary size reduction, we also added switches for the different functionality in the build scripts that is available with the SDK. By only adding functionality that your app needs in the binary, the size of the MSIX SDK binary size can be further reduced. 15 | 16 | You can get the latest SDK on GitHub. 17 | 18 |

MSIX SDK on GitHub

19 | 20 | -------------------------------------------------------------------------------- /msix-src/msix-sdk/release-notes/sdk-release-notes-1.6.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: MSIX SDK Release 1.6 release notes 3 | description: This article provides release notes for version 1.6 of the MSIX SDK. This SDK is available on GitHub. 4 | ms.date: 02/06/2018 5 | ms.topic: article 6 | keywords: windows 10, uwp, msix 7 | ms.custom: 19H1 8 | --- 9 | 10 | # MSIX SDK 1.6 update 11 | 12 | With the SDK release (1.6), we heard the feedback from our partners and added more APIs to provide developers with more options and flexibility in handling MSIX packages. 13 | 14 | ## UTF8 API Variants 15 | 16 | In this SDK release, we add about 14 new UTF8 API variants for existing API calls. With the inclusion of these new APIs, developers can choose to use the Utf8 variant for string manipulation according to their environment/platform. As with AppxPackaging APIs, the caller is responsible for deallocating the memory used by LPSTR* out parameters. 17 | 18 | The following are the new UTF8 interfaces: 19 | - IAppxBlockMapFileUtf8 20 | - IAppxBlockMapReaderUtf8 21 | - IAppxBundleManifestPackageInfoUtf8 22 | - IAppxBundleReaderUtf8 23 | - IAppxFactoryUtf8 24 | - IAppxFileUtf8 25 | - IAppxManifestApplicationUtf8 26 | - IAppxManifestPackageDependencyUtf8 27 | - IAppxManifestPackageIdUtf8 28 | - IAppxManifestPropertiesUtf8 29 | - IAppxManifestQualifiedResourceUtf8 30 | - IAppxManifestResourcesEnumeratorUtf8 31 | - IAppxManifestTargetDeviceFamilyUtf8 32 | - IAppxPackageReaderUtf8 33 | 34 | 35 | ## Override Language Selection 36 | 37 | By default, when handling app bundles, MSIX SDK returns the language package that is applicable by selecting the language that is also default on the system. This API allows the app to enumerate the language packages that are available and override the language package that will be returned while handling app bundles. 38 | 39 | ## Other updates and improvements 40 | 41 | In this update, 42 | - Update the OpenSSL lib dependency to 1.0.2q 43 | - Fixed how we handle international characters 44 | 45 | You can get the latest SDK on GitHub. 46 | 47 |

MSIX SDK on GitHub

48 | 49 | -------------------------------------------------------------------------------- /msix-src/msix-sdk/release-notes/sdk-release-notes-1.7.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: MSIX SDK Release 1.7 release notes 3 | description: This article provides release notes for version 1.7 of the MSIX SDK. This SDK is available on GitHub. 4 | ms.date: 08/05/2019 5 | ms.topic: article 6 | keywords: windows 10, uwp, msix 7 | ms.custom: 19H1 8 | --- 9 | 10 | # MSIX SDK 1.7 update 11 | 12 | With the SDK release (1.7), we heard the feedback from our partners and added more APIs to provide developers with more options and flexibility in handling MSIX packages. 13 | 14 | ## Create MSIX package using the MSIX SDK 15 | 16 | In this release you can now create an MSIX package using the MSIX SDK for Windows, MacOS and Linux. There are two ways to create a package: 17 | 18 | - Use the **makemsix** tool and specify an input directory and the name of the output package. 19 | 20 | ```console 21 | makemsix.exe pack -d -p [options] 22 | ``` 23 | 24 | - Use the `IAppxPackaging` APIs to create a package programmatically. Specifically, you can use `IAppxPackageWriter`, `IAppxPackageWriter3`, `IAppPackageWriterUtf8` and `IAppxPackageWriter3Utf8`. For an example that demonstrates how to use these APIs, see [**PackSample**](https://github.com/microsoft/msix-packaging/tree/master/sample/PackSample). 25 | 26 | ## Update to msix.dll 27 | 28 | This release adds the following interfaces to msix.dll: 29 | 30 | - `IAppxManifestReader4` 31 | - `IAppxPackageWriter` 32 | - `IAppxPackageWriter3` 33 | - `IAppxManifestOptionalPackageInfo` 34 | 35 | ## UTF8 API Variants 36 | 37 | This release adds several new UTF8 API variants for existing API calls. With the inclusion of these new APIs, developers can choose to use the Utf8 variant for string manipulation according to their environment/platform. As with AppxPackaging APIs, the caller is responsible for deallocating the memory used by LPSTR* out parameters. 38 | 39 | The following are the new UTF8 interfaces: 40 | 41 | - `IAppxPackageWriterUtf8` 42 | - `IAppxPackageWriter3Utf8` 43 | - `IAppxManifestOptionalPackageInfoUtf8` 44 | 45 | ## Updates to test infrastructure 46 | 47 | This release updates the test infrastructure to use [Catch2](https://github.com/catchorg/Catch2). Before this release, the SDK provided three different test implementations: 48 | 49 | - PowerShell script for Windows. 50 | - Shell script for Linux and macOS. 51 | - Common shared library for Android and iOS. 52 | 53 | This change removes the overhead of adding a test three times by simplifying the test infrastructure to a single implementation. 54 | 55 | You can get the latest SDK on GitHub. 56 | 57 |

MSIX SDK on GitHub

58 | -------------------------------------------------------------------------------- /msix-src/msix-sdk/sdk-overview.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: MSIX SDK 3 | description: MSIX SDK is an open source project that allows developers to use MSIX package format universally on all platforms. 4 | ms.date: 09/07/2018 5 | ms.topic: article 6 | keywords: windows 10, uwp, msix 7 | ms.custom: RS5 8 | --- 9 | 10 | # MSIX SDK 11 | 12 |

MSIX SDK on GitHub

13 | 14 | The MSIX SDK is an open source project that allows developers to use the MSIX package format universally on all platforms. This allows developers to build consistent experiences for their users on all platforms and distribute the experiences using the same package. The SDK provides guidance for developers to package their app content and build an app package manifest in a way that it can target the platforms of their choice. This enables developers to package their app content once instead of having to package for each platform. 15 | 16 | The SDK provides the APIs required to verify, validate and unpack the package contents from the MSIX package. Using the project, app developers don't have to worry about whether the package has been tampered with or if it can be trusted. It will perform tamper protection and signature validation checks before the app contents are unpacked. 17 | 18 | The SDK can be used by any cross platform client app that allows for third parties to build plugins or extensions. The client app developers can use the app extension model that is available on Windows 10 platform and use the MSIX SDK on the non-Windows 10 platforms. With the help of the SDK, third party developers building app extensions and plugins for the client app do not have to build a specific package for each platform. Instead, they build one package that is supported on Windows 10 and all the other platforms. With the SDK, app developers can choose specific platforms to support. 19 | 20 | One of the key differentiators of the MSIX package is the manifest file. The manifest file contains all the metadata regarding the package and specifies all the key information that the client app can access to make appropriate choices like applicability or supportability. The manifest file allows client app developers and third party developers more options and flexibility to communicate characteristics such as requirements, availability, and support. For more information about how to use the manifest file to distribute an MSIX package to Windows 10 and non-Windows 10 platforms, see [this article](sdk-guidance.md). 21 | 22 | ## Get more info 23 | 24 | MSIX SDK is an [open source project on GitHub](https://github.com/Microsoft/msix-packaging). The GitHub repo includes the full source and instructions for how to build the binaries for each platform. 25 | 26 | If you have feedback, please submit it on the [MSIX tech community site](https://techcommunity.microsoft.com/t5/MSIX/ct-p/MSIX). If there are issues or bugs that identified in the SDK, you can post them to the [issues page](https://github.com/Microsoft/msix-packaging/issues) for the MSIX SDK GitHub repo. 27 | -------------------------------------------------------------------------------- /msix-src/msix-server-2019.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: MSIX Support on Server 2019 3 | description: This article provides details on on how MSIX support on Server 2019 4 | ms.date: 01/16/2020 5 | ms.topic: article 6 | author: andreww-msft 7 | keywords: windows 10, windows 7, windows 8, Windows Server, uwp, msix, msixcore, 1709, 1703, 1607, 1511, 1507 8 | ms.custom: "RS5, seodec18" 9 | --- 10 | 11 | # MSIX support on Windows Server 2019 12 | 13 | MSIX is now supported on Windows Server 2019 (LTSC) with the Desktop Experience. This support enables you to distribute the same MSIX packages within your enterprise on both client and server SKUs, installing via **PowerShell** or installing directly via the [Package Manager API](/uwp/api/Windows.Management.Deployment.PackageManager). 14 | 15 | ## Considerations 16 | 17 | * The Microsoft Store and the Microsoft Store for Business are not supported on Windows Server 2019. All applications must be installed using **PowerShell**. 18 | * Because Windows Server 2019 is based on Windows 10, version 1809, it supports applications that have a minimum target version of **10.0.17763** or lower. 19 | * The following APIs and frameworks are not available on Windows Server 2019: 20 | * Microsoft Advertising 21 | * Geolocation 22 | * Cortana Search 23 | * In-app purchase 24 | * The following frameworks are not installed on Windows Server 2019. It is your responsibility to make sure they are installed with your app when needed. 25 | * .NET runtime 26 | * .NET Framework 27 | * VCLibs 28 | * The following package extensions are not supported on Windows Server 2019: 29 | * windows.firewallRules 30 | * windows.appExecutionAlias 31 | * windows.comServer 32 | * windows.comInterface 33 | * windows.posPaymentConnector 34 | * windows.dataProtection 35 | 36 | > [!NOTE] 37 | > Because Windows Server 2019 with the Desktop Experience does not support all features of Windows 10 client SKUs, we recommend you test applications on Windows Server 2019 before deploying in production. 38 | -------------------------------------------------------------------------------- /msix-src/package/bundling-overview.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Bundling MSIX packages 3 | description: An overview of MSIX Bundles 4 | ms.date: 02/05/2020 5 | ms.topic: article 6 | keywords: windows 10, msix 7 | ms.custom: "RS5, seodec18" 8 | --- 9 | 10 | # Bundling MSIX packages 11 | 12 | ## Overview 13 | 14 | An MSIX bundle is made up of multiple MSIX packages and it can reduce the size of the app that users download. App bundles are helpful for different architectures, language-specific assets, varying image-scale assets, or resources that apply to specific devices. By bundling multiple architectures versions of your application into one entity, only the bundle needs to be uploaded to your distribution location (instead of having one for each architecture). The Windows 10 deployment platform is aware of the .msixbundle package type and will only download the files that are applicable to a device's architecture. Keep in mind that if you decide to distribute an .msixbundle for a particular app, you cannot revert back to distributing just an MSIX package. 15 | 16 | If you're [packaging your application in Visual Studio](../package/packaging-uwp-apps.md), the Create Package Wizard gives you a "Generate app bundle" option during package creation. You can set this option to have Visual Studio generate an MSIX bundle for you. 17 | If you're generating MSIX packages using the [MSIX Packaging Tool](../packaging-tool/tool-overview.md) or [MakeAppx.exe](manual-packaging-root.md) you can take advantage of MakeAppx.exe to generate a bundle from individual packages e.g. after generating or converting an x86 and x64 MSIX package of your app you can use the process outlined below to bundle the packages using MakeAppx.exe. 18 | 19 | 20 | 21 | ## Additional Resources 22 | 23 | For more information about generating an MSIX bundle see: 24 | - [Creating a bundle using a directory structure](/windows/win32/appxpkg/make-appx-package--makeappx-exe-#to-create-a-package-bundle-using-a-directory-structure) 25 | - [Creating a bundle using a mapping file](/windows/win32/appxpkg/make-appx-package--makeappx-exe-#to-create-a-package-bundle-using-a-mapping-file) 26 | 27 | For more information about signing app packages with SignTool.exe, see [this article](../package/sign-app-package-using-signtool.md). 28 | 29 | -------------------------------------------------------------------------------- /msix-src/package/fx-packages.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Framework packages 3 | description: This topic contains a link to info about MSIX framework packages. 4 | ms.date: 03/02/2023 5 | ms.topic: article 6 | keywords: windows 11, uwp, desktop, msix 7 | --- 8 | 9 | # Framework packages 10 | 11 | See [Use MSIX framework packages dynamically from your desktop app](/windows/apps/desktop/modernize/framework-packages/). 12 | -------------------------------------------------------------------------------- /msix-src/package/images/appinstaller-screen.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/package/images/appinstaller-screen.png -------------------------------------------------------------------------------- /msix-src/package/images/bundle-combined.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/package/images/bundle-combined.png -------------------------------------------------------------------------------- /msix-src/package/images/msixpackage.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/package/images/msixpackage.png -------------------------------------------------------------------------------- /msix-src/package/images/package-signing2.PNG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/package/images/package-signing2.PNG -------------------------------------------------------------------------------- /msix-src/package/images/packaging-layout.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/package/images/packaging-layout.png -------------------------------------------------------------------------------- /msix-src/package/images/packaging-screen1.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/package/images/packaging-screen1.jpg -------------------------------------------------------------------------------- /msix-src/package/images/packaging-screen10.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/package/images/packaging-screen10.png -------------------------------------------------------------------------------- /msix-src/package/images/packaging-screen2.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/package/images/packaging-screen2.jpg -------------------------------------------------------------------------------- /msix-src/package/images/packaging-screen3.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/package/images/packaging-screen3.jpg -------------------------------------------------------------------------------- /msix-src/package/images/packaging-screen4.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/package/images/packaging-screen4.jpg -------------------------------------------------------------------------------- /msix-src/package/images/packaging-screen5.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/package/images/packaging-screen5.jpg -------------------------------------------------------------------------------- /msix-src/package/images/packaging-screen6.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/package/images/packaging-screen6.jpg -------------------------------------------------------------------------------- /msix-src/package/images/packaging-screen7.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/package/images/packaging-screen7.jpg -------------------------------------------------------------------------------- /msix-src/package/images/packaging-screen8.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/package/images/packaging-screen8.jpg -------------------------------------------------------------------------------- /msix-src/package/images/packaging-screen9.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/package/images/packaging-screen9.jpg -------------------------------------------------------------------------------- /msix-src/package/images/primary-bundle.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/package/images/primary-bundle.png -------------------------------------------------------------------------------- /msix-src/package/manual-packaging-root.md: -------------------------------------------------------------------------------- 1 | --- 2 | ms.assetid: ee51eae3-ed55-419e-ad74-6adf1e1fb8b9 3 | title: Package from the command line 4 | description: This section contains or links to articles about manually packaging Windows apps. 5 | ms.date: 01/30/2020 6 | ms.topic: article 7 | keywords: windows 10, uwp, packaging 8 | --- 9 | 10 | # Package from the command line 11 | 12 | If you don't develop your app in Visual Studio, you can use the MSIX command line tools to package and sign your applications. 13 | 14 | 15 | ## Purpose 16 | 17 | This section links to articles about manually packaging your app as an MSIX using command line tools. 18 | 19 | | Topic | Description | 20 | |-------|-------------| 21 | | [Generating package components ](../desktop/desktop-to-uwp-manual-conversion.md) | Create a package manifest and add Target-based unplated assets (optional) | 22 | | [Create an MSIX package or bundle with the MakeAppx.exe tool](create-app-package-with-makeappx-tool.md) | MakeAppx.exe creates, encrypts, decrypts, and extracts files from app packages and bundles. | 23 | | [Create a certificate for package signing](create-certificate-package-signing.md) | Create and export a certificate for app package signing with PowerShell tools. | 24 | | [Sign an app package using SignTool](sign-app-package-using-signtool.md) | Use SignTool to manually sign an app package with a certificate. | 25 | 26 | ### Advanced topics 27 | 28 | This section contains more advanced topics for componentizing a large and/or complex app for more efficient packaging and installation. 29 | 30 | > [!IMPORTANT] 31 | > If you intend to submit your app to the Store, you need to contact [Windows developer support](https://developer.microsoft.com/windows/support) and get approval to use any of the advanced features in this section. 32 | 33 | 34 | | Topic | Description | 35 | |-------|-------------| 36 | | [Package creation with the packaging layout](packaging-layout.md) | The packaging layout is a single document that describes packaging structure of the app. It specifies the bundles of an app (primary and optional), the packages in the bundles, and the files in the packages. | 37 | | [Introduction to asset packages](asset-packages.md) | Asset packages are a type of package that act as a centralized location for an application’s common files – effectively eliminating the necessity for duplicated files throughout its architecture packages. | 38 | | [Developing with asset packages and package folding](package-folding.md) | Learn how to efficiently organize your app with asset packages and package folding. | 39 | | [Flat bundle app packages](flat-bundles.md) | Describes how to create a flat bundle for your app’s package files. | 40 | 41 | -------------------------------------------------------------------------------- /msix-src/package/modification-package-developers.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Building an app with a modification package 3 | description: This article describes how modification packages will work with their app when it is packaged as an MSIX 4 | ms.date: 02/04/2020 5 | ms.topic: article 6 | keywords: windows 10, uwp, msix 7 | ms.custom: "RS5, seodec18" 8 | --- 9 | 10 | # Building an app with a modification package 11 | Modification packages allow IT Pros to customize their MSIX apps without having to repackage the app again. What this means is that when the IT Pro deploys the main app and the modification package and the user runs the app, the customization contained in the modification package will overlay on top of the main app such that it will feel like one app to the user. This is because modification packages run inside the main app's MSIX container and can only be accessed through the main app. Modification package example are plugin/addons, files and registry keys. This is something to keep in mind when developing your application, especially for enterprises. 12 | 13 | By having the main app and modification package model, as a developer, your enterprise customer will get the latest and greatest from you when you an update without needing to repackage. This is because the customization is all stored in the modification package which can be deployed and maintained independently. 14 | 15 | -------------------------------------------------------------------------------- /msix-src/package/streaming-install.md: -------------------------------------------------------------------------------- 1 | --- 2 | ms.assetid: df4d227c-21f9-4f99-9e95-3305b149d9c5 3 | title: App streaming install 4 | description: App streaming install enables you to specify which parts of your app you would like the Microsoft Store to download first. 5 | ms.date: 07/02/2019 6 | author: andreww-msft 7 | ms.author: andreww 8 | ms.topic: article 9 | keywords: windows 10, msix, uwp, streaming install 10 | --- 11 | 12 | # App streaming install 13 | 14 | App streaming install enables you to specify which parts of your app you would like the Microsoft Store to download first. When the essential files of the app are downloaded first, the user can launch and interact with the app while the rest of it finishes downloading in the background. 15 | 16 | To use app streaming install you'll need to divide your app's files into sections. To do this, you'll create a content group map, which is an XML file that's packaged with your app, allowing you to set download priority and order. See the topic linked below for more information. 17 | 18 | 19 | | Topic | Description | 20 | |-------|-------------| 21 | | [Create and convert a source content group map](create-cgm.md) | To get your app ready for streaming install, you'll need to create a content group map. This article will help you with the specifics of creating and converting a content group map while providing some tips and tricks along the way. | 22 | -------------------------------------------------------------------------------- /msix-src/package/unsigned-package.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Create an unsigned MSIX package 3 | description: This topic describes how to create and install an unsigned MSIX package 4 | ms.date: 05/26/2023 5 | ms.topic: article 6 | keywords: windows 11, uwp, desktop, msix 7 | --- 8 | 9 | # Create an unsigned MSIX package 10 | 11 | As of Windows 11, you can install your app via PowerShell without needing to sign your package. This feature is intended to make it easier for you to quickly test your app. Don't use this feature to distribute your app widely. 12 | 13 | ## Create an unsigned package 14 | 15 | An unsigned package must include a special OID (organization ID) value in its [Identity](/uwp/schemas/appxpackage/uapmanifestschema/element-identity) element in the manifest file, otherwise it won't be allowed to register. An unsigned package will never have the same identity as a package that's signed. That prevents unsigned packages from conflicting with, or spoofing the identity of, a signed package. 16 | 17 | Here's an example. 18 | 19 | ```xml 20 | ... 21 | 24 | ... 25 | ``` 26 | 27 | ## Install an unsigned package 28 | 29 | > [!IMPORTANT] 30 | > In most scenarios, you'll need to run PowerShell as administrator. See the details below. 31 | 32 | * To install an unsigned package, pass the `-AllowUnsigned` flag to the [Add-AppxPackage](/powershell/module/appx/add-appxpackage) command. 33 | * In most scenarios, the unsigned package will contain executable content; so you'll need to run PowerShell as administrator. That's because an unsigned package containing executable content must be installed for all users. Since that can affect more than just the current user, it requires administrator privilege. 34 | * If the unsigned package contains only non-executable content (for example, when you need to load only images, assets and other content, or script files) then administrator privilege is *not* needed, and a non-admin can install the package. 35 | 36 | Here's an example of the syntax. 37 | 38 | ```powershell 39 | Add-AppPackage -Path ".\MyEmployees.appx" -AllowUnsigned 40 | ``` 41 | 42 | When your app is ready to be distributed, you should ensure that the package is signed. Be sure to remove the special OID, and ensure that the publisher name is the same as the certificate subject name. 43 | 44 | ## Related topics 45 | 46 | * [Create hosted apps](/windows/uwp/launch-resume/hosted-apps) 47 | -------------------------------------------------------------------------------- /msix-src/packaging-tool/Quick-Create-VM.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: MSIX packaging environment on Hyper-V Quick Create 3 | description: Create a virtual environment for MSIX packaging projects using the Hyper-V Quick Create feature. 4 | ms.date: 04/04/2019 5 | ms.topic: article 6 | keywords: MSIX, MPT, MSIX Packaging Tool, Hyper-V Quick Create 7 | ms.custom: RS5 8 | --- 9 | 10 | # MSIX packaging environment on Hyper-V Quick Create 11 | 12 | You can create a virtual environment for MSIX packaging projects using the [Hyper-V Quick Create](/virtualization/hyper-v-on-windows/quick-start/quick-create-virtual-machine) feature. This feature is available starting in Windows 10, version 1709. 13 | 14 | To get started, type 'Hyper-V Quick Create' in your Start menu, select **MSIX Packaging Tool Environment**, and click **Create Virtual Machine**. After you finish the wizard, start the MSIX Packaging tool on the VM from the Start menu. Or if you have Hyper-V Manager open, Click 'Quick Create...' in the top right corner of the application and it will display the same UI. 15 | 16 | The MSIX Packaging Tool Environment is a custom Windows 10 evaluation build (version 1909) that includes the latest version of the MSIX Packaging Tool and other pre-requisites so that you can get started quickly with limited setup tasks. 17 | 18 | ![quickCreatepic1](images/QuickCreateVM.png) 19 | 20 | > [!NOTE] 21 | > This feature requires Hyper-V. You can learn more about Hyper-V and how to enable it [here](/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v). 22 | -------------------------------------------------------------------------------- /msix-src/packaging-tool/convert-an-installer-with-services.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Converting an installer with services 3 | description: This article explains how to convert an existing installer with services to MSIX using the MSIX Packaging Tool 4 | ms.date: 12/19/2019 5 | ms.topic: article 6 | keywords: windows 10, MSIX, MSIX Packaging Tool, services 7 | --- 8 | 9 | # Convert an installer that includes services 10 | 11 | Windows 10, version 2004, introduces support for running an MSIX package that includes services. You can use the MSIX Packaging Tool to take an existing installer with services and convert it to MSIX. This support is as of the January 2020 release of the [MSIX Packaging Tool](tool-overview.md)(1.2019.1220.0). Once you have a packaged MSIX with a service, it will require admin privileges to install on a machine. 12 | 13 | ## Instructions 14 | 15 | To convert an installer that includes services, use the MSIX Packaging Tool as you would with any [application package](create-app-package.md). Select an installer that has services, and you will see the **Services** report page before the final step to create your MSIX package. 16 | 17 | The **Services** report page lists services that were detected in your installer during conversion. Services that have all the information they need and are supported will be shown in the **Included** table. Services that need additional information, need a fix, or aren’t supported will be shown in the **Excluded** table. 18 | 19 | To fix a service or see additional data about the service, double-click the service entry in the table to view a pop-up with more information about the service. You can edit some of this information if you need to. 20 | 21 | - **Key name:** The name of the service. This is not editable. 22 | - **Description:** The description of the service entry. 23 | - **Display name:** The display name of the service. 24 | - **Image path:** Location of the service executable. This is not editable. 25 | - **Start account:** The start account for the service. 26 | - **Startup type:** Type of startup for the service. Supports **Automatic**, **Manual**, **Disabled**, and **Delayed**. 27 | - **Arguments:** Arguments to be run when the service starts. 28 | - **Dependencies:** Dependencies for the service. 29 | 30 | After a service has been fixed, you can move it to the **Included** table or you can choose to leave it in the **Excluded** table if you don’t want it in your final package. Then, you can continue to the final step to create your MSIX package. 31 | 32 | ## Known limitations 33 | 34 | The services executable path (also called the image path) is currently not editable. To fix any issues with your path, you must manually edit your service executable path before converting your installer. Alternatively, after conversion you can edit the manifest manually using the [Package Editor](package-editor.md) in the MSIX Packaging Tool. 35 | 36 | The Services report is currently not available in the **Package Editor**. You must manually edit the manifest to make changes to the services included in your MSIX package. 37 | 38 | We currently do not support services with dependencies outside the package. 39 | 40 | ## Add a service manually using your manifest 41 | 42 | If you are manually adding a service to your application, you will need to [add a service](/uwp/schemas/appxpackage/uapmanifestschema/element-desktop6-service) to your app manifest. This does require a [restricted capability](/windows/uwp/packaging/app-capability-declarations#restricted-capabilities) to add to your application. 43 | -------------------------------------------------------------------------------- /msix-src/packaging-tool/duplicate-tool-settings-across-devices.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Duplicate MSIX Packaging Tool Settings across multiple devices 3 | description: Learn how to duplicate your MSIX Packaging Tool Settings across multiple devices 4 | author: sharlaakers 5 | ms.date: 02/06/2019 6 | ms.topic: article 7 | keywords: windows 10, uwp, msix 8 | --- 9 | 10 | # Duplicate MSIX Packaging Tool Settings across multiple devices 11 | 12 | Follow these simple steps to duplicate settings for the MSIX Packaging Tool across multiple devices, or to back up and restore settings if you need to re-image a device. This feature is available starting in version 1.2019.110.0 of the MSIX Packaging Tool. 13 | 14 | ## Build the baseline 15 | 16 | 1. On a device with the MSIX Packaging Tool installed, click the settings Icon. 17 | 2. Configure the settings to meet the specific requirements of your environment. 18 | > [!NOTE] 19 | > This generally means tweaking the file and registry exclusions but can include any of the settings. 20 | 3. After you configure the settings, make sure you click Save settings and then close the tool. 21 | 22 | ## Back up the settings configuration 23 | 24 | From the device with the configured baseline, copy the following file to a known good location, such as network server share. 25 | 26 | * C:\Users\\%username%\AppData\Local\Packages\Microsoft.MsixPackagingTool_8wekyb3d8bbwe\LocalState\settings.xml 27 | 28 | > [!NOTE] 29 | > Make sure this file isn't deleted or altered, because it will be your template for all other installations. 30 | 31 | ## Restore the settings configuration 32 | 33 | When a new device is setup with the MSIX Packaging Tool installed, copy the settings.xml from the known good location back to the local device: 34 | 35 | * C:\Users\\%username%\AppData\Local\Packages\Microsoft.MsixPackagingTool_8wekyb3d8bbwe\LocalState\settings.xml 36 | 37 | ## Considerations 38 | 39 | * Make sure the \ entry is removed or is a valid location for a user. If the value is not provided or the location is invalid, the tool will default to C:\Users\\%username%\Desktop. 40 | 41 | * Settings files should only be copied to the same version of the packaging tool or a later version. Settings may not be honored if the version in the settings.xml is copied to an older version of the tool. We recommend that you always use the latest version of the tool for the latest fixes and for the best packaging experience. 42 | -------------------------------------------------------------------------------- /msix-src/packaging-tool/edit-icons-and-assets.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Edit icons and assets using the MSIX Packaging Tool 3 | description: Describes how to edit icons and assets during the app conversion process while using the MSIX Packaging Tool. 4 | ms.date: 06/27/2019 5 | ms.topic: article 6 | keywords: windows 10, uwp, msix 7 | ms.custom: "RS5, seodec18" 8 | --- 9 | 10 | # Edit icons and assets using the MSIX Packaging Tool 11 | 12 | There are several ways you can modify your app package assets during the conversion process while using the MSIX Packaging Tool: 13 | 14 | * You can modify your app package assets during the conversion process. 15 | * After your package has been created, you can modify your app package assets via the [Package editor](package-editor.md). 16 | 17 | Refer to [Design guidelines for Windows app icons](/windows/apps/design/style/iconography/app-icon-design) as you make your modifications. 18 | 19 | ## Modify assets during the conversion process 20 | 21 | During the monitored installation phase of the MSIX Packaging Tool workflow, the MSIX Packaging Tool will capture any changes that you make to files or folders for your application. If you change your assets during the monitoring, those changes will be captured in your final package. 22 | 23 | ## Modify assets after your package has been created 24 | 25 | To modify your app package assets after you create your MSIX package, open your MSIX package in [Package editor](package-editor.md), and then open the **Package files** page. You can delete existing assets or add new icons or assets. 26 | 27 | - To add a new asset file, right-click the assets folder, and select **Add file** or **Add folder**. 28 | - To delete an existing asset file, right-click the file and select **Delete**. 29 | 30 | To verify your asset changes, go to the **Package information** page and open your manifest file. Confirm that the assets you added or removed are represented in the [uap:VisualElements](/uwp/schemas/appxpackage/uapmanifestschema/element-uap-visualelements) node. The manifest reference needs to be specific, but the asset files can be named whatever you like. 31 | -------------------------------------------------------------------------------- /msix-src/packaging-tool/images/PackageEditorPkgInfo1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/packaging-tool/images/PackageEditorPkgInfo1.png -------------------------------------------------------------------------------- /msix-src/packaging-tool/images/PackageEditorPkgInfo2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/packaging-tool/images/PackageEditorPkgInfo2.png -------------------------------------------------------------------------------- /msix-src/packaging-tool/images/QuickCreateVM.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/packaging-tool/images/QuickCreateVM.png -------------------------------------------------------------------------------- /msix-src/packaging-tool/images/bundle-pic1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/packaging-tool/images/bundle-pic1.png -------------------------------------------------------------------------------- /msix-src/packaging-tool/images/mpt_blog_0.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/packaging-tool/images/mpt_blog_0.jpg -------------------------------------------------------------------------------- /msix-src/packaging-tool/images/mpt_blog_1.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/packaging-tool/images/mpt_blog_1.jpg -------------------------------------------------------------------------------- /msix-src/packaging-tool/images/mpt_blog_10.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/packaging-tool/images/mpt_blog_10.jpg -------------------------------------------------------------------------------- /msix-src/packaging-tool/images/mpt_blog_11.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/packaging-tool/images/mpt_blog_11.jpg -------------------------------------------------------------------------------- /msix-src/packaging-tool/images/mpt_blog_2.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/packaging-tool/images/mpt_blog_2.jpg -------------------------------------------------------------------------------- /msix-src/packaging-tool/images/mpt_blog_3.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/packaging-tool/images/mpt_blog_3.jpg -------------------------------------------------------------------------------- /msix-src/packaging-tool/images/mpt_blog_4.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/packaging-tool/images/mpt_blog_4.jpg -------------------------------------------------------------------------------- /msix-src/packaging-tool/images/mpt_blog_5.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/packaging-tool/images/mpt_blog_5.jpg -------------------------------------------------------------------------------- /msix-src/packaging-tool/images/mpt_blog_6.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/packaging-tool/images/mpt_blog_6.jpg -------------------------------------------------------------------------------- /msix-src/packaging-tool/images/mpt_blog_7.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/packaging-tool/images/mpt_blog_7.jpg -------------------------------------------------------------------------------- /msix-src/packaging-tool/images/mpt_blog_9.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/packaging-tool/images/mpt_blog_9.jpg -------------------------------------------------------------------------------- /msix-src/packaging-tool/images/pic1.PNG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/packaging-tool/images/pic1.PNG -------------------------------------------------------------------------------- /msix-src/packaging-tool/images/pic11.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/packaging-tool/images/pic11.png -------------------------------------------------------------------------------- /msix-src/packaging-tool/images/pic12.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/packaging-tool/images/pic12.png -------------------------------------------------------------------------------- /msix-src/packaging-tool/images/pic13.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/packaging-tool/images/pic13.png -------------------------------------------------------------------------------- /msix-src/packaging-tool/images/pic2.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/packaging-tool/images/pic2.jpg -------------------------------------------------------------------------------- /msix-src/packaging-tool/images/pic3.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/packaging-tool/images/pic3.jpg -------------------------------------------------------------------------------- /msix-src/packaging-tool/images/pic4.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/packaging-tool/images/pic4.png -------------------------------------------------------------------------------- /msix-src/packaging-tool/images/pic5.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/packaging-tool/images/pic5.png -------------------------------------------------------------------------------- /msix-src/packaging-tool/images/pic6.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/packaging-tool/images/pic6.png -------------------------------------------------------------------------------- /msix-src/packaging-tool/images/pic7.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/packaging-tool/images/pic7.png -------------------------------------------------------------------------------- /msix-src/packaging-tool/images/pic8.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/packaging-tool/images/pic8.png -------------------------------------------------------------------------------- /msix-src/packaging-tool/images/pic9.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/packaging-tool/images/pic9.png -------------------------------------------------------------------------------- /msix-src/packaging-tool/media/package-analyzer/screenshot-2023-10-06-014557.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/packaging-tool/media/package-analyzer/screenshot-2023-10-06-014557.jpg -------------------------------------------------------------------------------- /msix-src/packaging-tool/package-analyzer.md: -------------------------------------------------------------------------------- 1 | --- 2 | # Required metadata 3 | # For more information, see https://review.learn.microsoft.com/help/platform/learn-editor-add-metadata?branch=main 4 | # For valid values of ms.service, ms.prod, and ms.topic, see https://review.learn.microsoft.com/help/platform/metadata-taxonomies?branch=main 5 | 6 | title: Package Analyzer 7 | description: feature in MSIX Packaging tool that analyzes the package. It then detects errors and suggests fixes. 8 | author: fiza-azmi # GitHub alias 9 | ms.author: fizaazmi # Microsoft alias 10 | ms.topic: article 11 | ms.date: 10/06/2023 12 | --- 13 | 14 | # Analyze and resolve runtime issues 15 | 16 | The **Package Analyzer** in [MSIX Packaging tool](/windows/msix/packaging-tool/tool-overview) provisions runtime analysis of an MSIX package and suggests remediations to fix post-conversion issues seamlessly. This feature simplifies conversion and packaging workflows, and saves time and effort by streamlining the debugging and application of fixes. 17 | 18 | ## Key features 19 | 20 | 1: **Analyze Package:** 21 | The analyze feature analyzes input MSIX package trace logs during runtime with one simple click 22 | 23 | 2: **Automated remediation:** 24 | Based on the analysis, automated suggestions are provided by MSIX Packaging tool to fix the detected runtime errors. The fixes are then applied on saving the package. 25 | 26 | ## Package Analyzer 27 | 28 | Once you have converted an app to MSIX format, to begin analysis: 29 | 30 | 1. Select **Package Editor** in the MSIX Packaging tool and Browse the MSIX package of your choice 31 | 2. Once you sign the package with a certificate, navigate to the **Package Analyzer** tab 32 | 3. Click on **Analyze Package** button 33 | 4. The tool will automatically start examining the package for any issues. Play around with features of your application for a while to test functionality before stopping analysis 34 | 5. Once you click on **Stop Analysis**, the tool will suggest remediations to fix runtime issues with your application 35 | 36 | ![Package-Analyzer](media/package-analyzer/screenshot-2023-10-06-014557.jpg) 37 | 38 | 39 | 6. Review the suggestions, unchecking fixes you don’t deem necessary, and click on **Save** 40 | 1. A new package will automatically be created with the selected fixes 41 | 42 | ## Supported fixes 43 | 44 | Currently the following fixes are supported in Preview, and we are continuing to iterate on them further to cover more fixups and make your MSIX conversion processes more effortless. 45 | 46 | 1. RegLegacyFixups(PSF) 47 | 2. Installed location Virtualization 48 | 3. SearchPathoverride 49 | 50 | 51 | 52 | 53 | 54 | -------------------------------------------------------------------------------- /msix-src/packaging-tool/package-conversion-command-line.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Create a package using the command line interface 3 | description: This article describes how to create an MSIX package using the command line interface for the MSIX Packaging Tool. 4 | ms.date: 02/11/2019 5 | ms.topic: article 6 | keywords: windows 10, uwp 7 | ms.custom: RS5 8 | --- 9 | 10 | # Conversion with the command line 11 | 12 | ## Automate conversion of Windows installers to MSIX packages using scripts 13 | 14 |

Get MSIX Packaging Tool

15 | 16 | The MSIX Packaging Tool supports a command line interface for creating MSIX application packages. This enables you to automate the process of repackaging app installers and perform bulk conversions. 17 | 18 | For sample PowerShell and Bash scripts that demonstrate how to automate the process of packaging, signing, managing and distributing MSIX packages, see the [scripts](https://github.com/microsoft/MSIX-Toolkit/tree/master/Scripts) folder of the MSIX Toolkit. 19 | 20 | ## Use the command line with the Command Prompt 21 | 22 | To create a new MSIX package for your application, run the `MsixPackagingTool.exe create-package` command in an administrator Command prompt window. Please note this is an [app execution alias](/windows/apps/desktop/modernize/desktop-to-uwp-extensions#start-your-application-by-using-an-alias) to make it easier to run the application without specifying the full path. 23 | 24 | Here are the parameters that can be passed as command line arguments(case sensitive): 25 | 26 | |**Parameter** | **Description**| 27 | |---------|---------| 28 | |-? --help |Show help information| 29 | |--template | [required] path to the conversion template XML file containing package information and settings for this conversion| 30 | |--virtualMachinePassword | [optional] The password for the Virtual Machine to be used for the conversion environment. Note: The template file must contain a VirtualMachine element and the Settings::AllowPromptForPassword attribute must not be set to true.| 31 | |--machinePassword |[optional] The password for the remote machine to be used for the conversion environment. Note: The template file must contain a RemoteMachine or VirtualMachine element and the Settings::AllowPromptForPassword attribute must not be set to true.| 32 | |--resume |[optional] Used to resume the conversion flow after a reboot.| 33 | |-v --verbose |[optional] Print verbose logs to the console.| 34 | 35 | Examples: 36 | 37 | ```console 38 | 39 | MsixPackagingTool.exe create-package --template c:\users\documents\ConversionTemplate.xml -v 40 | 41 | MSIXPackagingTool.exe create-package --template c:\users\documents\ConversionTemplate.xml --virtualMachinePassword pswd112893 42 | 43 | ``` 44 | 45 | > [!NOTE] 46 | > App-V 5.x conversion is currently supported to be converted throught the command line. This includes capabilities. 47 | 48 | You can [generate a command line template file](generate-template-file.md) through the MSIX Packaging Tool by going through the conversion process with an application or you can build one from our sample template. 49 | -------------------------------------------------------------------------------- /msix-src/packaging-tool/prepare-your-environment.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: prepare your environment for conversion 3 | description: Learn how to correctly prepare your environment for conversion to convert existing installers to MSIX. 4 | ms.date: 01/27/2020 5 | ms.topic: article 6 | keywords: msix 7 | --- 8 | 9 | # Prepare your environment for conversion 10 | 11 | Preparing your conversion environment is an important step in the conversion process. The following recommendations will help to ensure your success when you are converting your existing installers to MSIX. 12 | 13 | - The minimum OS version requirement for the MSIX Packaging Tool is Windows 10 1809. We understand that not everyone is on the Windows 10 October 2018 Update or even Windows 10. Therefore, we recommend that you create a clean VM that is pre-configured for the min version of support for the MSIX Packaging Tool. Deployment of the generated MSIX package has different support requirements. 14 | 15 | - A clean machine for conversion is important because during the installation step of the MSIX Packaging Tool, we will be listening to everything in the environment to capture what the installer is doing. A clean machine means that there aren't extraneous apps or services running on your machine that could get captured in your package. 16 | 17 | - We recommend configuring the conversion machine to mimic the environment where the MSIX package will be run, so if there are services or policies that will be there, you can test that the package will actually work. 18 | 19 | - Your conversion environment should match the architecture of where you will be deploying the application. For example, if you are going to deploy your MSIX package on an x64 machine, you should perform the conversion on an x64 machine. 20 | 21 | - If this isn't something you have we offer a **Quick Create VM**, the [MSIX Packaging Tool Environment](quick-create-vm.md) in Hyper-V, which is ready to go with conversion with Windows 10 1809 and the latest version of the MSIX Packaging Tool. 22 | 23 | - Follow the best practices recommendations for [setting up the MSIX Packaging Tool](tool-best-practices.md) (or tool of your choice), then create a checkpoint for the VM. This way you can use the VM to convert, revert to your previous checkpoint, and it will be a clean, configured machine ready for conversion again or for verifying your MSIX package converted successfully. 24 | 25 | - Its also good to know what kind of dependencies you have so that you can understand which ones you should run with your app and which should be packaged as a modification package. For example, if you have runtime dependencies, it’s a good idea to include those in your main application. If you have a plug in, you should package that as a modification package to associate with your main application. 26 | 27 | - If you want to perform your conversion on a remote machine, you will need to do some additional [set-up](remote-conversion-setup.md) to enable it for conversion. 28 | -------------------------------------------------------------------------------- /msix-src/packaging-tool/support-restart.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Support for desktop installers that require device restart 3 | description: Describes how to support desktop installers that require device restart. 4 | ms.date: 04/04/2019 5 | ms.topic: article 6 | keywords: MSIX, MPT, MSIX Packaging Tool, 1709, 16299 7 | ms.custom: RS5 8 | --- 9 | 10 | # Support for desktop installers that require device restart 11 | 12 | Beginning in the 1.2019.701.0 version of the MSIX Packaging Tool, you can trigger a restart during conversion for your installer. 13 | 14 | Restarts are supported both through our interactive UI and through the command line. In addition, through the command line, you can also specify you want to auto-login after the restart to have a seamless hands-free conversion. 15 | 16 | You can specify which exit codes indicate a restart in the Settings > [Installer exit codes](tool-best-practices.md#other-settings) page. 17 | 18 | You can trigger a restart through the UI during your conversion workflow or through the start menu of your conversion machine. After the restart has happened, you will return to the same place you were in the tool to continue with your conversion. 19 | 20 | We always want to hear from you, so if you have any feedback, please be sure to [file feedback](./insider-program.md#share-your-feedback) with us. 21 | -------------------------------------------------------------------------------- /msix-src/psf/images/add-reference-packaging-project.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/add-reference-packaging-project.png -------------------------------------------------------------------------------- /msix-src/psf/images/appxmanifest-application-executable.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/appxmanifest-application-executable.png -------------------------------------------------------------------------------- /msix-src/psf/images/appxmanifest-application-id.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/appxmanifest-application-id.png -------------------------------------------------------------------------------- /msix-src/psf/images/appxmanifest-application-processexecutable.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/appxmanifest-application-processexecutable.png -------------------------------------------------------------------------------- /msix-src/psf/images/appxmanifest-application-workingdirectory.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/appxmanifest-application-workingdirectory.png -------------------------------------------------------------------------------- /msix-src/psf/images/blank-app.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/blank-app.png -------------------------------------------------------------------------------- /msix-src/psf/images/blank-solution.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/blank-solution.png -------------------------------------------------------------------------------- /msix-src/psf/images/configjson-complete.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/configjson-complete.png -------------------------------------------------------------------------------- /msix-src/psf/images/contosoapp-fileproperties-target-parameter.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/contosoapp-fileproperties-target-parameter.png -------------------------------------------------------------------------------- /msix-src/psf/images/contosoapp-fileproperties-target.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/contosoapp-fileproperties-target.png -------------------------------------------------------------------------------- /msix-src/psf/images/contosoexpense-add-psf-files.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/contosoexpense-add-psf-files.png -------------------------------------------------------------------------------- /msix-src/psf/images/contosoexpense-appdata-icon.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/contosoexpense-appdata-icon.png -------------------------------------------------------------------------------- /msix-src/psf/images/contosoexpense-changevalues-shortcut.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/contosoexpense-changevalues-shortcut.png -------------------------------------------------------------------------------- /msix-src/psf/images/contosoexpense-config-json.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/contosoexpense-config-json.png -------------------------------------------------------------------------------- /msix-src/psf/images/contosoexpense-create-alias.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/contosoexpense-create-alias.png -------------------------------------------------------------------------------- /msix-src/psf/images/contosoexpense-edit-manifest.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/contosoexpense-edit-manifest.png -------------------------------------------------------------------------------- /msix-src/psf/images/contosoexpense-edit-mpt.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/contosoexpense-edit-mpt.png -------------------------------------------------------------------------------- /msix-src/psf/images/contosoexpense-final-shortcut.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/contosoexpense-final-shortcut.png -------------------------------------------------------------------------------- /msix-src/psf/images/contosoexpense-finish-creating-appshortcut.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/contosoexpense-finish-creating-appshortcut.png -------------------------------------------------------------------------------- /msix-src/psf/images/contosoexpense-generic-shortcut.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/contosoexpense-generic-shortcut.png -------------------------------------------------------------------------------- /msix-src/psf/images/contosoexpense-new-appshortcut.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/contosoexpense-new-appshortcut.png -------------------------------------------------------------------------------- /msix-src/psf/images/contosoexpense-newpath-shortcut.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/contosoexpense-newpath-shortcut.png -------------------------------------------------------------------------------- /msix-src/psf/images/contosoexpense-psf-added-files.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/contosoexpense-psf-added-files.png -------------------------------------------------------------------------------- /msix-src/psf/images/contosoexpense-psf-manifest.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/contosoexpense-psf-manifest.png -------------------------------------------------------------------------------- /msix-src/psf/images/contosoexpense-run-through-alias.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/contosoexpense-run-through-alias.png -------------------------------------------------------------------------------- /msix-src/psf/images/contosoexpense.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/contosoexpense.png -------------------------------------------------------------------------------- /msix-src/psf/images/get-psf-from-github-releases.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/get-psf-from-github-releases.png -------------------------------------------------------------------------------- /msix-src/psf/images/iso-option.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/iso-option.png -------------------------------------------------------------------------------- /msix-src/psf/images/package-project-references.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/package-project-references.png -------------------------------------------------------------------------------- /msix-src/psf/images/package-project-template.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/package-project-template.png -------------------------------------------------------------------------------- /msix-src/psf/images/package-support-framework-2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/package-support-framework-2.png -------------------------------------------------------------------------------- /msix-src/psf/images/package-support-framework.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/package-support-framework.png -------------------------------------------------------------------------------- /msix-src/psf/images/package_binaries.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/package_binaries.png -------------------------------------------------------------------------------- /msix-src/psf/images/package_contents.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/package_contents.png -------------------------------------------------------------------------------- /msix-src/psf/images/procmon-filterdialog-completed.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/procmon-filterdialog-completed.png -------------------------------------------------------------------------------- /msix-src/psf/images/procmon-filterdialog-processname-psfsample.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/procmon-filterdialog-processname-psfsample.png -------------------------------------------------------------------------------- /msix-src/psf/images/procmon-filterdialog-result-success.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/procmon-filterdialog-result-success.png -------------------------------------------------------------------------------- /msix-src/psf/images/procmon-psfsampleapp-readfailure.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/procmon-psfsampleapp-readfailure.png -------------------------------------------------------------------------------- /msix-src/psf/images/procmon-psfsampleapp-writefailure.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/procmon-psfsampleapp-writefailure.png -------------------------------------------------------------------------------- /msix-src/psf/images/procmon_app_filter.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/procmon_app_filter.png -------------------------------------------------------------------------------- /msix-src/psf/images/procmon_config_txt.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/procmon_config_txt.png -------------------------------------------------------------------------------- /msix-src/psf/images/procmon_events.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/procmon_events.png -------------------------------------------------------------------------------- /msix-src/psf/images/procmon_exclude_success.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/procmon_exclude_success.png -------------------------------------------------------------------------------- /msix-src/psf/images/procmon_logfile.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/procmon_logfile.png -------------------------------------------------------------------------------- /msix-src/psf/images/psf-package.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/psf-package.png -------------------------------------------------------------------------------- /msix-src/psf/images/psfsampleapp_config_txt.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/psfsampleapp_config_txt.png -------------------------------------------------------------------------------- /msix-src/psf/images/reference-fix.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/reference-fix.png -------------------------------------------------------------------------------- /msix-src/psf/images/runtime-fix-library.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/runtime-fix-library.png -------------------------------------------------------------------------------- /msix-src/psf/images/runtime-fix-project-structure.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/runtime-fix-project-structure.png -------------------------------------------------------------------------------- /msix-src/psf/images/set-startup-project.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/set-startup-project.png -------------------------------------------------------------------------------- /msix-src/psf/images/shim-exe-reference.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/shim-exe-reference.png -------------------------------------------------------------------------------- /msix-src/psf/images/traceshim_accessdenied.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/traceshim_accessdenied.png -------------------------------------------------------------------------------- /msix-src/psf/images/traceshim_filenotfound.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/images/traceshim_filenotfound.png -------------------------------------------------------------------------------- /msix-src/psf/media/psf-integration-with-mpt/psf-fixups-tab-in-mpt.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/media/psf-integration-with-mpt/psf-fixups-tab-in-mpt.jpg -------------------------------------------------------------------------------- /msix-src/psf/media/psf-integration-with-mpt/psf-fixups-tab-in-mpt1.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/MicrosoftDocs/msix-docs/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/psf/media/psf-integration-with-mpt/psf-fixups-tab-in-mpt1.jpg -------------------------------------------------------------------------------- /msix-src/psf/psf-integration-with-mpt.md: -------------------------------------------------------------------------------- 1 | --- 2 | # Required metadata 3 | # For more information, see https://review.learn.microsoft.com/help/platform/learn-editor-add-metadata?branch=main 4 | # For valid values of ms.service, ms.prod, and ms.topic, see https://review.learn.microsoft.com/help/platform/metadata-taxonomies?branch=main 5 | 6 | title: Automated PSF config generation 7 | description: Integration of PSF with MSIX Packaging tool to simplify conversion by automating PSF config file generation 8 | author: fiza-azmi # GitHub alias 9 | ms.author: fizaazmi # Microsoft alias 10 | ms.topic: article 11 | ms.date: 10/06/2023 12 | --- 13 | 14 | # Automated PSF config generation 15 | 16 | This article talks about the integration of adding Package Support Framework (PSF) fixups with the MSIX Packaging Tool. This integration aims to simplify applying PSF fixups by automating the PSF config.json file generation, eliminating the need for manual configuration and reducing the potential for errors. 17 | 18 | ## Prerequisites 19 | 20 | To try out this feature, download [MSIX Packaging Tool](https://www.microsoft.com/p/msix-packaging-tool/9n5lw3jbcxkf) from Microsoft Store 21 | 22 | ### Automatically generate PSF config.json 23 | 24 | To apply known fixups, 25 | 26 | 1. Launch the MSIX Packaging Tool, select to __Package Editor__ and navigate to the __PSF Fixups__ tab. 27 | 28 | 1. Select the __Application ID__ as present in the manifest. The Executable path will be populated automatically. 29 | 30 | 1. Select the __Fixup__ that you want to apply and fill all the mandatory parameters in the right pane. 31 | 32 | 1. You can review the configuration applied by clicking on __Preview config.json__ and then click on __Save__ to automatically apply the fixups. 33 | 34 | 35 | ![PSF fixups tab in MPT](media/psf-integration-with-mpt/psf-fixups-tab-in-mpt1.jpg) 36 | 37 | >[!VIDEO 3cc16061-205e-409b-ab27-48fcd1373360] 38 | 39 | ### Supported PSF Features 40 | 41 | #### 1. Application Fixups 42 | >[!VIDEO a34d5fc5-1a5d-4b43-995d-c3271038ae3d] 43 | 44 | -Working Directory 45 | -Command Line Arguments  46 | 47 | #### 2. PowerShell Start/End Script  48 | 49 | >[!VIDEO 6a54e797-89f4-43df-a526-95c9625faa13] 50 | 51 | #### 3. File Redirection Fixup  52 | -Package Relative 53 | 54 | >[!VIDEO 5e1e2ccd-e444-4ded-a092-e715118c7da7] 55 | 56 | -Package Drive Relative 57 | 58 | >[!VIDEO 4ed29340-57f7-40f6-ab08-db6c3f6cffcf] 59 | 60 | -Known Folder 61 | 62 | >[!VIDEO 27299008-c0fa-4507-9ba6-7a0baad81dc0] 63 | 64 | #### 4. Reg Legacy Fixup  65 | 66 | -ModifyKeyAccess 67 | 68 | >[!VIDEO f42e8fbb-3e27-43d1-a82d-cc614e73f42f] 69 | 70 | -FakeDelete 71 | 72 | >[!VIDEO d1ca3935-a6b6-4d87-8638-acc16ef2fe77] 73 | 74 | -DeletionMarker 75 | 76 | >[!VIDEO 9a2321af-b3ae-498f-8d14-04aa626af615] 77 | 78 | -Redirect 79 | 80 | >[!VIDEO 190013af-c1af-4bec-a005-6cecc623f9dc] 81 | 82 | #### 5. Environment Variable Fixup 83 | 84 | >[!VIDEO 46417fed-8732-4735-bb85-7db856888e6f] 85 | 86 | #### 6. Dynamic Library Fixup 87 | 88 | >[!VIDEO cfa60160-9aef-4a28-93e4-2a25512044d8] 89 | 90 | 91 | 92 | 93 | -------------------------------------------------------------------------------- /msix-src/render.yml: -------------------------------------------------------------------------------- 1 | ### YamlMime:ContextObject 2 | uhfHeaderId: MSDocsHeader-MSIX 3 | searchScope: 4 | - UWP 5 | breadcrumb_path: ./breadcrumb/toc.yml 6 | toc_rel: ./toc.yml 7 | -------------------------------------------------------------------------------- /msix-src/toolkit/msix-toolkit-appinstallerfilebuilder.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: AppInstaller File Builder tool 3 | description: This article provides details about the AppInstaller File Builder tool in the MSIX Toolkit. 4 | ms.date: 1/23/2020 5 | ms.topic: article 6 | keywords: windows 10, msix, msix toolkit 7 | ms.custom: 19H1 8 | --- 9 | 10 | # AppInstaller File Builder tool 11 | 12 | The [AppInstaller File Builder tool](https://github.com/microsoft/MSIX-Toolkit/tree/master/AppInstallerFileBuilder) in the MSIX toolkit can be used to configure a packaged app to check back to a central source for updates. This tool aids in the construction of an AppInstaller (.appinstaller) file. The AppInstaller file can be used with different [deployment options](../desktop/managing-your-msix-deployment-overview.md). 13 | 14 | ## Create an AppInstaller file 15 | 16 | 1. Download the [AppInstaller File Builder](https://github.com/microsoft/MSIX-Toolkit/releases/download/1.3.3/AppInstallerFileBuilder_1.2019.1001.0.msix) 17 | 2. Install and launch the **AppInstaller File Builder** app. 18 | 3. Select the **Get Package Info** button and browse to the MSIX app that you would like to install using the AppInstaller file. 19 | 4. Specify the update options that you would like the app package to have. 20 | > [!Note] 21 | > Options may vary based on selected minimum operating system version. **Check for updates on app launch** must be enabled within the tool to see or configure these values. 22 | 5. Continue through the wizard, adding [optional packages](../package/optional-packages.md), [modification packages](/windows/msix/modification-packages), [related packages](../package/optional-packages.md) and dependencies as required. 23 | 6. Select the **Generate** button after reviewing the Summary details to create the AppInstaller file. 24 | -------------------------------------------------------------------------------- /msix-src/toolkit/msix-toolkit-overview.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: MSIX Toolkit 3 | description: This article provides details about the available MSIX toolkit. 4 | ms.date: 1/23/2020 5 | ms.topic: article 6 | keywords: windows 10, msix, msix toolkit 7 | ms.custom: 19H1 8 | --- 9 | 10 | # MSIX Toolkit 11 | 12 | The [MSIX Toolkit](https://aka.ms/msixtoolkit) is a collection of tools and scripts that enable IT Pros and developers to build and manage MSIX packages. The toolkit is an open source project on GitHub to allow customers and enthusiasts to contribute directly and provide suggestions and feedback on the content that is available. 13 | 14 | ## Principles 15 | 16 | The MSIX Toolkit follows these principles: 17 | 18 | * It is a community-led space where customers can freely contribute source code along with binaries and executables. 19 | * Users can't post artifacts that don't have a corresponding source code unless they are redistributables. 20 | * Until there is sufficient community involvement, a Microsoft employee will oversee the pull requests. 21 | * All contributed source code must include a readme file with detailed instructions on the setup and how to build the source code. 22 | 23 | ## How to contribute 24 | 25 | The [MSIX Toolkit](https://aka.ms/msixtoolkit) repository accepts external contributions via a [pull request from a fork](https://help.github.com/en/articles/creating-a-pull-request-from-a-fork). Create only a single pull request per issue, while keeping the pull requests as small and contained to to a single scenario as possible. Before we can accept a pull request from you, you must sign a Contributor License Agreement (CLA). 26 | 27 | See the [readme](https://github.com/microsoft/MSIX-Toolkit/blob/master/README.md) for more details on how to contribute. 28 | 29 | ## Microsoft-provided content in the toolkit 30 | 31 | Microsoft includes the following scripts, redistributables, and tools in the MSIX toolkit. 32 | 33 | ## Scripts 34 | 35 | | Name | Description | 36 | |------|-------------| 37 | | [BulkConversion](msix-toolkit-msixbatchconversion.md) | A set of PowerShell scripts that provide the ability to bulk conversion of applications into the MSIX application package format. | 38 | | [ModifyPackagePublisher](msix-toolkit-modifypackagepublisher.md) | A PowerShell script that provides the ability to update the publisher information of an MSIX application to align with the certificate used to sign the application. | 39 | 40 | ## Redistributables 41 | 42 | | Name | Description| 43 | |------|------------| 44 | | [Redist.x64](https://github.com/microsoft/MSIX-Toolkit/tree/master/WindowsSDK/10/10.0.20348.0/x64) | Includes the binaries and tools from the Windows 10 SDK that are essential while working with MSIX packages. These binaries are intended for a device operating on a 64-bit architecture. | 45 | | [Redist.x86](https://github.com/microsoft/MSIX-Toolkit/tree/master/WindowsSDK/10/10.0.20348.0/x86) | Includes the binaries and tools from the Windows 10 SDK that are essential while working with MSIX packages. These binaries are intended for a device operating on a 32-bit architecture. | 46 | 47 | The redistributables (x86/x64) are used with the Microsoft MSIX Toolkit scripts providing the required executables. 48 | 49 | ## Tools 50 | 51 | | Name | Description| 52 | |------|------------| 53 | | [AppInstallerFileBuilder](./msix-toolkit-appinstallerfilebuilder.md) | The AppInstaller File Builder tool is a Windows 10 app that simplifies the creation of AppInstaller files. This app allows the user to specify the app packages they would like to distribute, along with the update options. | 54 | --------------------------------------------------------------------------------