Symptoms

We have two SmOs / Service Broker Instances in our project that are based on the WCF EndPoint Service Broker. When creating a package the Service Broker Instances are not included in the package and the SmOs show no dependencies. More so if I go to manually include the Service Instances in the package PandD does not even show them as an option to manually select.

When deploying this package we get errors about missing dependencies even though it is not possible to include them when packaging. I was able to work around this by manually creating the Service Instance on the target environment with the appropriate GUID and then manually matching the missing dependency at from the deployment wizard.
 

Diagnoses

This is expected behavior for 4.6.8.
 

Resolution

Labs has confirm the from 4.6.10 the following services can be packaged by PandD again

WCFServiceType
AzureServicetype
Crm5EntityServiceType
CrmEntityServiceType