We found another one (looks that way anyway).

Our installer registers a Service on the target machine, but it should only do so if a particular feature is set to install. In SB, we set the Service to be dependent on the feature, since the exe that runs as the service is only installed if the feature is installed.

However, we've found that the service is still registered even when the feature is not installed. The service isn't running, and indeed cannot start since the exe that it needs isn't actually there - but I wasn't expecting the Service to be registered when the dependent feature isn't installed.

Is this a SB bug, or did I miss something in the setup?