New Post: Interplay between Solution Name, , and ApplicationName

Tom,

I did a "bad thing", and BTDF didn't protect me from myself... (Rule #1 - do no harm).

After customizing my .btdfproj file, I was testing it by doing menu: Tools/BTDF/Build Server Deploy MSI to get things tested.
BUT, Oops, then I clicked by mistake on Tools/BTDF/Deploy BizTalk Solution.
I had not yet built my binding file or SSO file.

So here's what happened:
1) It deleted my ABC App (my last exported binding is two weeks ago, so now I might have to reconstruct a few things).

Perhaps first step is to save a backup of the existing bindings. 

2) So I can add <ApplicationName>ABC</ApplicationName> to .btdfproj file? There wasn't one there.
3) When it was done, I saw an two empty apps: 1) ABC, and 2) ABC_All_BizTalk.

ABC is the AppName in each of the three Biztalk Project properties.

I did a query on [BizTalkMgmtDb].[dbo].[bts_application] and see the ABC_All_BizTalk was created today 13 minutes before ABC. So I think BTDF must have created it and not sure why. (That is my Solution Name.)

I saw this error on the my output log.

C:\Program Files (x86)\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets : warning : PortBindings.xml : No matches found for XPath expression '//ApplicationName'. [E:\Source\neal\SCRUM\ABC\Deployment\Deployment.btdfproj]

So that implies it might be getting the applicationName from PortBindingMaster which I had not yet configured.

I will rebuild my app and bindings now, and continue on...

Neal