Optional packages with executable code
Optional packages with executable code are useful for dividing a large or complex app, or for adding on 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.
- Visual Studio 2017, version 15.7
- Windows 10, version 1709
- Windows 10, version 1709 SDK
To get the latest development tools, see Downloads and tools for Windows 10.
To submit an app that uses optional packages and/or related sets to the Store, you will need permission. Optional packages and related sets can be used for Line of Business (LOB) or enterprise apps without Dev Center permission if they are not submitted to the Store. See Windows developer support to get permission to submit an app that uses optional packages and related sets.
C++ Optional packages with executable code
To load code from a C++ optional package, see the OptionalPackageSample repository on GitHub. The OptionalPackageDLL shows how to create a project with code that can be executed from the main package. The MyMainApp project demonstrates how to load code from the OptionalPackageDLL.dll file.
C# Optional packages with executable code
To get started building an optional code package in C#, follow the below steps to configure your solution:
Create a new UWP application with the minimum version set to the Windows 10 Fall Creators Update SDK (Build 16299) or higher.
Add a new Optional Code Package (Universal Windows) project to the solution. Ensure the Minimum Version and Target Version match that of your main app.
If you plan to submit your apps to the Store, right click on both projects and select Store -> Associate App with the Store...
Package.appxmanifestfile of the main app and find the
Identity Namevalue. Make a note of this value for the next step.
Open the optional app package's
Package.appxmanifestfile and find the
uap3:MainAppPackageDependency Namevalue. Update the
uap3:MainAppPackageDependency Namevalue to match the
Identity Namevalue of the main app package from the previous step.
Here's an example of the
Identityfrom the main app's
<Identity Name="12345.MainAppProject" Publisher="CN=PublisherName" Version="18.104.22.168" />
The optional app package's
uap3:MainPackageDependencyneeds to be updated to match the main app's
<uap3:MainPackageDependency Name="12345.MainAppProjectTest" />
Bundle.mapping.txtfile to the main app. Follow the steps in this Related sets section to create a related set containing both apps.
Build the optional package project and then navigate to the package Reference folder in the output from the build found at
..\[PathToOptionalPackageProject]\bin\[architecture]\[configuration]\Reference. Note that you can choose any architecture in the path to the Reference folder since the
.winmdfile (step 8) is architecture independent.
Add a reference from the main app project to the
.winmdfile found in this folder. Every time you change the API surface area in the optional package project, this
.winmdfile must be updated. This reference provides the main app project with the necessary information to compile.
In the main app project, navigate to the project build properties and select Compile with .NET Native tool chain. Currently, only debugging in .NET Native is supported for optional code package creation in C#. Go to the project debug properties and select Deploy optional packages. This will ensure that both packages are in sync whenever you deploy the main app project.
Once you're finished with these steps, you can add code to the optional package project as if it were a managed WinRT Component project. To access the code in the main app project, call the public methods exposed in the optional package project.