search

BTDF / CodePlexDiscussions

0 stars 0 forks source link

Discussion: Remove a Biztalk application as part of the deployment #29

Open tfabraham opened 6 years ago

tfabraham commented 6 years ago

MatthewCorr[5/15/2014 12:48:01 PM] Hello,

This is a bit of an unusual question!

We have 5 solutions. 4 of them are BizTalk applications and have a BTDF config for each and they all work correctly. The 5th project is a group of common DLLs that just need to be GAC'ed and SSO config data inserted. I was hoping to use the BTDF for this project, as in the future some BizTalk artefacts may be included and it also gives us a consistent approach for deployment.

I have been able to config the deployment config file so it just deployed the Components and SSO config, but it still (understandably) creates an empty BizTalk Application.

Is there a way as a post step of the deployment to just remove the empty application as it's not needed?

Something to run: "btstask RemoveApp -ApplicationName:CommonApp"

Thanks!

tfabraham commented 6 years ago

tfabraham You can add a step to the deployment to delete the application, but then when you go to undeploy, the undeploy script will abort because the app doesn't exist.

I've done it both ways, but when I've had common .NET assemblies used by BizTalk apps, I've also just created an MSI using WiX. That way you don't have any ties to BizTalk or the Deployment Framework.

Thanks, Tom

tfabraham commented 6 years ago

MatthewCorr Thanks for the feedback.

I think we will just have an empty BizTalk app, so the deployment and undeployment will work. The ability to utilise the SSO config (needed for the common app) via the excel spreadsheet is too tempting to give up.