This is one of those quirks that really annoys me when developing with BizTalk. Basically I just tweaked the name of a pipeline to match new naming standards, then deployed the pipeline. I then went to deploy an orchestration for the same BizTalk application. The deploy fails because Visual Studio attempts to use an out of date binding that refers to the old pipeline name which of course it can no longer find. Deleting the offending receive location doesn’t even remedy the situation.
I’m logging this for future reference as I always forget the location. The binding files Visual Studio uses can be found at C:\Documents and Settings\<user account>\Application Data\Microsoft\BizTalk Server\Deployment\BindingFiles. Either tweak them or simply delete them and rebind manually in the administration console.