- This topic has 2 replies, 1 voice, and was last updated 9 years, 6 months ago by
.
-
Posts
-
-
—————————
I have a large biztalk application consisting of 17 receive locations.
We have generated an MSI using the feature provided in 2006 for deploying this app into production and it is working fine since a month.
Now due to a new change request, we need one more receive location and a new dll to be deployed into production.I do not want to uninstall the entire application and recreate the MSI just to deploy these minor changes.
Is there any easy way to create an MSI for this "incremental" changes only?
Please advice
Reg,
anony
-
When you generate the MSI deployment package, you get to choose which resources are included. So, you can ONLY include the changed dll.
As for bindings, I'd suggest exporting out the entire binding, opening up the XML file, and removing everything but the new receive port/location. Then in production, deploy the MSI, import the MSI (to get the orchestration changes to take effect), and then import the binding.
-
I wish we had a tool such as what RedGate offers for SQL Server sync. What a great time saver that is! I would absolutely love a tool like that for BizTalk were you could see your Dev/Test server on the left and Production on the right – and easily and visibly see the differences between the two… sync individual binding (ports), resources (assemblies), etc.
As expensive as BizTalk is, you’d think MS would offer a better set of support / admin tools to go with it.
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.