Should be possible to attach a ProgId directly to a component, without a COM registration

[fredemmott]

For example, ProgIds are Microsoft's recommended (and more flexible) way to register file associations.

Example wxs: https://github.com/OpenKneeboard/OpenKneeboard/blob/2316b1290fef72750f0485a6ec0b618db04af4ca/installer/OpenKneeboardPluginFileType.wxs

[oleg-shilo]

I have updated the ProgId implementation and from the next release you can place the ProgId entity outside of the COM registration:

// under the root dir
var project =
    new Project("MyProduct",
        new Dir(@"%ProgramFiles%\My Company\My Product",
            new ProgId
            {
                Id = "PROG.ID.8",
                Description = "Version independent ProgID "
            },

// or even under the project root
var project =
    new Project("MyProduct",
        new ProgId
        {
            Id = "PROG.ID.8",
            Description = "Version independent ProgID "
        },
        new Dir(@"%ProgramFiles%\My Company\My Product",

it will emit the ProgId element in the first parent component:

<Component Id="Component.MyApp.exe_3459324387" Guid="6f330b47-2577-43ad-9095-18614c7a0c75">
  <ProgId Id="PROG.ID.8" Description="Version independent ProgID " />
  <File Id="MyApp.exe_3459324387" Source="Files\Bin\MyApp.exe">

Please note that while it seems to work, it does not exactly align with WixSharp paradigm, which encourages setup definition with a component-less mindset. This is because components in MSI are kinda "the blast from the past" (24 years ago to be precise). As many other over-engineered concepts like minor-update, MSM etc.

Don't get me wrong you can use any MSI feature as you wish, it's simply there will be limits on how much component exposure WixSharp will offer. Though in your case of ProgId we are perfectly OK.

[oleg-shilo]

Done. Please update to v2.4.4