Hi Rohan,
Assuming that you took this from the Visual Studio Output window, I believe that the log output you pasted is coming from BTSTask.exe, not the Deployment Framework. If you look backwards (earlier) in the log file from that point, you should find the BTSTask.exe command line. I suggest that you dispense with testing your entire deployment and focus on that command line. Just run it directly from a Command Prompt as admin. You should see the same output.
It should be as simple as:
BTSTask.exe AddResource -Type:BizTalkAssembly -Source:"..\Project\bin\debug\Communication.Orch.CommunicationDocument.dll" -ApplicationName:"MyAppName" -Options:GacOnAdd,GacOnImport,GacOnInstall
I also have to ask -- you are not using the Deploy menu in Visual Studio, right? You should have the Deploy checkbox in Configuration Manager unchecked for all BizTalk projects. All bindings-related configuration should come long after the orchestration deployment during the ImportBindings step.
Thanks,
Tom
Assuming that you took this from the Visual Studio Output window, I believe that the log output you pasted is coming from BTSTask.exe, not the Deployment Framework. If you look backwards (earlier) in the log file from that point, you should find the BTSTask.exe command line. I suggest that you dispense with testing your entire deployment and focus on that command line. Just run it directly from a Command Prompt as admin. You should see the same output.
It should be as simple as:
BTSTask.exe AddResource -Type:BizTalkAssembly -Source:"..\Project\bin\debug\Communication.Orch.CommunicationDocument.dll" -ApplicationName:"MyAppName" -Options:GacOnAdd,GacOnImport,GacOnInstall
I also have to ask -- you are not using the Deploy menu in Visual Studio, right? You should have the Deploy checkbox in Configuration Manager unchecked for all BizTalk projects. All bindings-related configuration should come long after the orchestration deployment during the ImportBindings step.
Thanks,
Tom