After the Deployment Type Extension file (*.cmdtx) is created, you are expected to generate a Windows Installer file (*.msi) which contains the *.cmdtx file and the UX files. The Windows Installer needs to copy the files into the correct locations and register the custom extension with the site server.
The basic contents of the Windows Installer file are shown below:
Create an installer from your application Once your project has been built, you can create an installer from it. Create a folder where the installers will be created, specifically in our workspace (C: Users sdkca Desktop electron-workspace) with the name you want, in this case it will be myapp-source-built-installers. Create a MSIX package with our conversion tool with all other installers. It must be running Windows 10, version 1809, or a later version of Windows. Under Choose the installer you want to package, find the installer on your machine. If you do not have an installer, you may skip this step. We do recommend that you sign your package.
To Create the Windows Installer File (*.msi)
Generate a Windows Installer file which contains the *.cmdtx file, and UX files. The Windows Installer file will be responsible for installing the UX files in the correct locations, using the standards defined by the Admin Console team. Basically, this will involve including the following files:
UX Assembly, e.g. AdminUI.DeploymentType.<AssemblySuffix>.dll
This file is required and contains the UX implementation, which is then bound to the Configuration Manager console using the below XML files.
The Installer should copy this file to smsAdminConsolebin.
CreateApp_<TechnologyID>.xml
This file is required and provides the console extension for the Create Application Wizard.
The Installer should copy this file to smsAdminConsoleXmlStorageExtensionsForms.
CreateDeploymentWizard_<TechnologyID>.xml
This file is required and provides the console extension for the Create Deployment Type Wizard.
The Installer should copy this file to smsAdminConsoleXmlStorageExtensionsForms.
The Logitech® Wireless Keyboard K360—beautifully convenient, conveniently compact with a familiar layout. Setup takes seconds—you simply plug the wireless receiver into a USB port, pull the battery tab and start using your keyboard right away without software. Whisper-quiet, framed keys.
<TechnologyID>DeploymentTypePropertySheet.xml
This file is required and provides the Deployment Type property page.
The Installer should copy this file to smsAdminConsoleXmlStorageForms.
The Windows Installer file should contain code to invoke the DeploymentTypeExtender.Extend method, which is located in the Microsoft.ConfigurationManagement.ApplicationManagement namespace. This will then register the extension files for a given site server computer. For an administrator console computer, this will initialize the cache for that user. The Extend method call requires the *.cmdtx file created earlier.
Make a standard WqlConnectionManager connection to the site server.
Call the Extend method, passing the *cmdtx file, the ConnectionManagerBase object through an instance of ConsoleDcmConnection for the method connection parameter, and the connection path (example below).
Warning
In order to use ConsoleDcmConnection, you will need to add an assembly reference to AdminUI.DcmObjectWrapper.dll.
Client Installation (HandlerApplication.zip)
To install the client extension files, either as part of the HandlerApplication or as a separate installation:
Compile the AppSynclet MOF file. On the client, compile the custom synclet MOF file to create the necessary instance of the CCM_AppHandler class and the corresponding instances of the CCM_HandlerSynclet classes.
Copy the handler .dll to the Configuration Manager client directory and register the .dll on the system.
Note
The handler .dll must be compiled to match the operating system – either 32-bit or 64-bit.