https:\/\/www.firegiant.com\/wix\/tutorial\/<\/u><\/a>)<\/p>\nBefore start, we need to link the setup project with our dll project.<\/p>\n
Right-click on the setup project “References” item and choose “Add Reference\u2026”.
\n![\"\"](\"\/wp-content\/uploads\/2023\/03\/image17-300x68.png\")
<\/p>\n
Select the “Project” tab, highlight your project, Add it and close this window.<\/p>\n
Let’s look the first segment:<\/p>\n
<<\/span>Product<\/span> Id<\/span>=\"*\"<\/span> Name<\/span>=\"myExtSetup\"<\/span> Language<\/span>=\"1033\"<\/span> Version<\/span>=\"1.0.0.0\"<\/span> Manufacturer<\/span>=\"\"<\/span> UpgradeCode<\/span>=\"99ff1cbe-xxxx-xxxx-xxxx-6913cf65xxxx\"><\/span>\n <<\/span>Package<\/span> InstallerVersion<\/span>=\"200\"<\/span> Compressed<\/span>=\"yes\"<\/span> InstallScope<\/span>=\"perMachine\" \/><\/span>\n\n <<\/span>MajorUpgrade<\/span> DowngradeErrorMessage<\/span>=\"A newer version of [ProductName] is already installed.\" \/><\/span>\n <<\/span>MediaTemplate<\/span> \/><\/span>\n <<\/span>Feature<\/span> Id<\/span>=\"ProductFeature\"<\/span> Title<\/span>=\"myExtSetup\"<\/span> Level<\/span>=\"1\"><\/span>\n <<\/span>ComponentGroupRef<\/span> Id<\/span>=\"ProductComponents\" \/><\/span>\n <\/<\/span>Feature<\/span>><\/span>\n<\/<\/span>Product<\/span>><\/span><\/pre>\nThese are general information about your MSI. Change the Name and the Manufacturer as you want but keep everything else as-is for now.<\/p>\n
Note that Id=”*” means that product Id will be automatically generated on build time. You don’t have to care about it. Upgrade code is much more important as this will be the key in case of multiple releases. If you keep the upgrade code unchanged and increment the Version number, you will be able to handle correctly automatic version replacement.<\/p>\n
Remember, our extension, like the console, is only 32bits. So add the Platform=”x86″ property to the “Package” tag like this:<\/p>\n
<<\/span>Package<\/span> InstallerVersion<\/span>=\"200\"<\/span> Compressed<\/span>=\"yes\"<\/span> InstallScope<\/span>=\"perMachine\"<\/span> Platform<\/u><\/span>=\"x86\"<\/u><\/span> \/><\/pre>\nIf you want your\u00a0installer to include all file in a single MSI\u00a0file ( by opposition to an MSI with separate Cab files) modify “MediaTemplate” like this :<\/p>\n
<<\/span>MediaTemplate<\/span> \/><\/span> => <<\/span>MediaTemplate<\/span> EmbedCab<\/span>=\"yes\" \/><\/span><\/pre>\nA brief explanation about features and Components:<\/p>\n
\n- every single object (like a file or a registry key) are components.<\/li>\n
- Components can be grouped in a ComponentGroup<\/li>\n
- A feature is a group of components that must be installed at once. This is what is presented to the user during a common install sequence to let them choose what they want. Components can be shared between different Features.<\/li>\n<\/ul>\n
We will create simple MSI with no graphical interface. As users won’t have any choice to make, a ingle feature will be enough.<\/p>\n
Change this section to something more adapted like :<\/p>\n
<<\/span>Feature<\/span> Id<\/span>=\"MyDeviceExt\"<\/span> Title<\/span>=\"Device Right click extension\"<\/span> Level<\/span>=\"1\"><\/span>\n <<\/span>ComponentGroupRef<\/span> Id<\/span>=\"ProductComponents\" \/><\/span>\n<\/<\/span>Feature<\/span>><\/span><\/pre>\nLet the “ComponentGroupRef” as-is for now. We will change it later.<\/p>\n
Then comes the directory section:<\/p>\n
<<\/span>Fragment<\/span>><\/span>\n <<\/span>Directory<\/span> Id<\/span>=\"TARGETDIR\"<\/span> Name<\/span>=\"SourceDir\"><\/span>\n <<\/span>Directory<\/span> Id<\/span>=\"ProgramFilesFolder\"><\/span>\n <<\/span>Directory<\/span> Id<\/span>=\"INSTALLFOLDER\"<\/span> Name<\/span>=\"myExtSetup\" \/><\/span>\n <\/<\/span>Directory<\/span>><\/span>\n <\/<\/span>Directory<\/span>><\/span>\n<\/<\/span>Fragment<\/span>><\/span><\/pre>\nThis will create a “myExtSetup” folder under “program Files(x86)” (remember the platform property). Let’s change that to create first a folder with our company name then a subfolder for our extension:<\/p>\n
<<\/span>Fragment<\/span>><\/span>\n <<\/span>Directory<\/span> Id<\/span>=\"TARGETDIR\"<\/span> Name<\/span>=\"SourceDir\"><\/span>\n <<\/span>Directory<\/span> Id<\/span>=\"ProgramFilesFolder\"><\/span>\n <<\/span>Directory<\/span> Id<\/span>=\"NOBUR_INC\"<\/span> Name<\/span>=\"Nobur inc.\" ><\/span>\n <<\/span>Directory<\/span> Id<\/span>=\"INSTALLFOLDER\"<\/span> Name<\/span>=\"Sccm Device Extension\" \/><\/span>\n <\/<\/span>Directory<\/span>><\/span>\n <\/<\/span>Directory<\/span>><\/span>\n <\/<\/span>Directory<\/span>><\/span>\n<\/<\/span>Fragment<\/span>><\/span><\/pre>\nWhen choosing an Id, don’t forget they must :<\/p>\n
\n- be unique in the file<\/li>\n
- contains only alphanumerical characters and underscores (_). Spaces are forbidden.<\/li>\n
- never start with a number<\/li>\n<\/ul>\n
Now the last part of the file.<\/p>\n
<<\/span>Fragment<\/span>><\/span>\n <<\/span>ComponentGroup<\/span> Id<\/span>=\"ProductComponents\"<\/span> Directory<\/span>=\"INSTALLFOLDER\"><\/span>\n <!-- TODO: Remove the comments around this Component element and the ComponentRef below in order to add resources to this installer. --><\/span>\n <!-- <Component Id=\"ProductComponent\"> --><\/span>\n <!-- TODO: Insert files, registry keys, and other resources here. --><\/span>\n <!-- <\/Component> --><\/span>\n <\/<\/span>ComponentGroup<\/span>><\/span>\n<\/<\/span>Fragment<\/span>><\/span><\/pre>\nThere we add our dll like this :<\/p>\n
<Fragment<\/span>><\/span>\n <<\/span>ComponentGroup<\/span> Id<\/span>=\"deviceExtComponents\"<\/span> Directory=\"INSTALLFOLDER\"><\/span>\n <<\/span>Component<\/span> Id<\/span>=\"deviceExtdll\"><\/span>\n <<\/span>File<\/span> Source<\/span>=\"$(var.MyFirstExtension.TargetPath)\"<\/span> DiskId<\/span>=\"1\"\/><\/span>\n <\/<\/span>Component<\/span>><\/span>\n <\/<\/span>ComponentGroup<\/span>><\/span>\n<\/<\/span>Fragment<\/span>><\/span><\/pre>\nThis instructs Wix to place the file generated in the “MyFirstExtension” project (represented by this variable: $(var.MyFirstExtension.TargetPath)) into the folder identified by “INSTALLFOLDER”. As we embed all the files into a unique MSI, you don’t have to care about the DiskId=”1″ parameter.<\/p>\n
Go back to the feature list and change the id of the componentGroupRef to reflect our new componentGroup Id<\/p>\n
<<\/span>ComponentGroupRef<\/span> Id=\"deviceExtComponents<\/u>\" \/><\/span><\/span><\/pre>\nNow, if you build this solution you will get a working\u00a0MSI file\u00a0that will deploy your Dll. This is not enough as we also need to deploy 2 XML files into the console directory.<\/p>\n
This is much harder than what we already did. Are you ready?<\/p>\n
First, we need to include our XML extension file into our project. Right-click on the “MyFirstExtension” project then select “Add” => “Existing Item\u2026”. Browse your disk to the place you saved our extension XML and add it. Now that is has been imported, rename it to mark it as a template:
\n![\"\"](\"\/wp-content\/uploads\/2023\/03\/image19.png\")
<\/p>\n
We will modify it a little to make more flexible (remember that the path to our dll in hardly coded into it). Double click on it to start edition and replace all the path targeting our Dll by something like a tag.<\/p>\n
My file will look like something like this:<\/p>\n
<<\/span>ActionDescription<\/span> Class<\/span>=\"AssemblyType\"<\/span> DisplayName<\/span>=\"show collections\"<\/span> MnemonicDisplayName<\/span>=\"show collections\"<\/span> Description<\/span>=\"Shows the list of collection IDs this device is member of\"><\/span>\n <<\/span>ImagesDescription<\/span>><\/span>\n <<\/span>ResourceAssembly<\/span>><\/span>\n <<\/span>Assembly<\/span>><\/span>[INSTALLFLD]<\/em><\/strong>MyFirstExtension.dll<<\/span>\/Assembly<\/span>><\/span>\n <<\/span>Type<\/span>><\/span>MyFirstExtension.Properties.Resources.resources<\/<\/span>Type<\/span>><\/span>\n <\/<\/span>ResourceAssembly<\/span>><\/span>\n <<\/span>ImageResourceName<\/span>><\/span>collinfo<\/<\/span>ImageResourceName<\/span>
![\"\"](\"\/wp-content\/uploads\/2023\/03\/image16-300x160.png\")
<\/p>\n