From time to time a developer will ask for help with Parameterization where they just can’t seem to get it working for some specific scenario. Often this is just an XPath bug or fat finger issue. In two seperate instances now simply deleting the existing parameter node in the parameters.xml and recreating it solves the problem. I have compared the two versions (old/new) in BeyondCompare and see not differences whatsoever. So I have no idea why this works but it does.
“deleting the existing parameter node in the parameters.xml and recreating it solves the problem”
In the latest case, they needed to replace the inner text for an xml node in the web.config. As far as I know there is no way to replace only the inner text of a node with WebDeploy Parameterization. The workaround is to replace the entire node. This isn’t ideal because you have to encode xml for the parameter value but it works.
Check out Elliott’s post for more details.