Visual Studio stores binding files for BizTalk Server project assemblies. Those files are used when BizTalk application is redeployed using VS. This way you may remove, i.e. orchestration assembly from BizTalk application resources and still have your orchestrations fully bound when you deploy the assembly again.
But sometimes the binding file that VS stores may get out of sync with your current solution and then you won’t be able to deploy the solution on your development machine anymore. Errors may be various, including:
Failed to add resource(s). Change requests failed for some resources. BizTalkAssemblyResourceManager failed to complete end type change request. Failed to update binding information. Could not enlist orchestration ‘[…]Orchestrations.CreateConstructor,[…]Orchestrations, Version=126.96.36.199, Culture=neutral, PublicKeyToken=[…]’. Could not enlist orchestration ‘[…]Orchestrations.CreateConstructor’. All orchestration ports must be bound and the host must be set.
Solving the issue requires removing invalid assembly binding from C:\Users\[user]\AppData\Roaming\Microsoft\BizTalk Server\Deployment\BindingFiles folder.