The Deployment Framework for BizTalk is the most powerful and customizable, yet easy-to-use toolkit for deploying and configuring your BizTalk solutions.
MIT License
53
stars
24
forks
source link
MSI Uninstall should not remove last settingsfilepath from registry #379
I am using BTDF 5.5 and are very happy so far but I found an issue around MSI uninstall and quick deploy (I am aware when it is safe to use quick deploy).
Here is my workflow:
changing code in VS
commit to TFS
continous build produces an MSI
on each teststage server (manually for now):
uninstall old solution via "add/remove programs" (this step removes the registry key which stores the last used settingsfile)
install new MSI from build server without deploying anything
running "Quick Deploy" from start menu => results in error because no settingsfile was selected
bounce host instances
Is there another workflow I am expected to run?
I am thinking about caching the settingsfilepath before uninstalling and restoring it after install.
Hi!
I am using BTDF 5.5 and are very happy so far but I found an issue around MSI uninstall and quick deploy (I am aware when it is safe to use quick deploy).
Here is my workflow:
changing code in VS commit to TFS continous build produces an MSI
on each teststage server (manually for now):
uninstall old solution via "add/remove programs" (this step removes the registry key which stores the last used settingsfile) install new MSI from build server without deploying anything running "Quick Deploy" from start menu => results in error because no settingsfile was selected
bounce host instances
Is there another workflow I am expected to run?
I am thinking about caching the settingsfilepath before uninstalling and restoring it after install.
opinions / help?
This work item was migrated from CodePlex
CodePlex work item ID: '10944' Vote count: '1'