Thanks Tom.
I went through the tutorials. As developers donot have access to Production environments, we are providing .bat file along with MSI to do the deployment. In the .bat file we are calling it in the following sequence.
1) Undeploy Application 1 ( if exists)
2) UnInstall Application 1 ( If exists)
3) Uninstall Application 2 ( If exists)
4) Install First Application
5) Install Second Application
6) Deploy First Application
7) Deploy Second application
Initially, I was not able to find syntax for UnDeploy. After some research, Found the following syntax
%BTDFMSBuildPath% Deployment.btdfproj /p:%PARMS% /target:Undeploy /l:FileLogger,Microsoft.Build.Engine;logfile=%ApplicationInstallPath%\DeployResults\DeployResults.txt
It worked fine. .bat file is now all ready for complete automation.
Thanks a lot for your help! Biztalk Deployment Framefork is such a great product. It made life lot easier.
Thanks,
Pavan
I went through the tutorials. As developers donot have access to Production environments, we are providing .bat file along with MSI to do the deployment. In the .bat file we are calling it in the following sequence.
1) Undeploy Application 1 ( if exists)
2) UnInstall Application 1 ( If exists)
3) Uninstall Application 2 ( If exists)
4) Install First Application
5) Install Second Application
6) Deploy First Application
7) Deploy Second application
Initially, I was not able to find syntax for UnDeploy. After some research, Found the following syntax
%BTDFMSBuildPath% Deployment.btdfproj /p:%PARMS% /target:Undeploy /l:FileLogger,Microsoft.Build.Engine;logfile=%ApplicationInstallPath%\DeployResults\DeployResults.txt
It worked fine. .bat file is now all ready for complete automation.
Thanks a lot for your help! Biztalk Deployment Framefork is such a great product. It made life lot easier.
Thanks,
Pavan