This has happened a couple of times. It is either a bug or a feature that I don't know about. I will describe the situation, the work around and ask if anyone else has seen it and if it is going to be fixed.
Windows 2008 R2 virtual machine, VS2010, BizTalk 2010 (ver 3.9.469.0)
The immediate problem: I set up a new receive location for an existing Receive Port. I also set up a send port to subscribe. I did some testing and wasn't happy with the maps, schemas, etc for the VS2010 project so I deleted the receive location, send port, etc. and removed the assemblies using the BizTalk administrator. I made all the changes in the VS2010 project and redeployed and got an error
Error 23 Failed to add resource(s). Change requests failed for some resources. BizTalkAssemblyResourceManager failed to complete end type change request. Failed to update binding information. Receive Location 'EDI856TPProcIn' has no Transport type specified.
The work-around is simple enough, I just re-create the receive location. I want to know why does the VS2010 project remember the receive location? Is there some way to make VS2010 forget it?
Thanks
Harold
Harold Rosenkrans
I just wanted to add an addendum - I recreated the receive location against the same receive port. It looked ok (this has worked in the past) but this time when I opened the property sheet for the receive port and clicked on the Inbound Maps (there used to be a reference to a map from the VS2010 project that I had removed) I get the error:
Failed to enable constrains. One or more rows contain values violating non-null, unique or foreign-key constraints (System.Data).
There was one time when I had a similar problem I had to start up an earlier snapshot of the virtual machine - the BizTalk database basically got corrupted.