Wix# is trying to get away from the concept of installation Component
as it's hard to find today a valid use-case when the deployment requirements force user/developer to deal with the product sub-parts individually. Even MSI support for
doesn't justify existence of Components
as features can directly group deployment artefacts instead if their groups.
are legacy entities that came from the times when it was believed that the deployment life cycle has higher resolution than a product scope (e.g. components can be updated without updating the product). And today even MS completely abandoned
idea (e.g. ClickOnce).
Well this is a theory :)
On practical level MSI just forces you to have components and Wix# complies by creating them automatically by wrapping every artefact into a component. If you want to inject an extra component or extra items into it you will need to do it via XML injection
(see InjectXML sample).
However... I haven't seen yet (even once) any problem that was caused by the Wix# component hiding "attitude". Thus there is a good chance that your problem can be solved with the existing component handling.
Just going through the sample you provided the link for I see that most likely the pseudo-code below will produce the required WXS:
DriverInstaller = new DriverInstaller
Legacy = true