I am using msdeploy V3 quite successfully in various advanced scenarios. One problem however I was not able to solve is, to have encrypted passwords in parameter files. These passwords are used together with a username to set the identity of our application pools. I am using a parameter file per environment like DEV, TRAIN and PROD.
The current solution I have is msbuild based where msbuild calls msdeploy. Because of the above problem, I have taken the password parameter out of the parameter file and pass it via -setPara:password=mypassword. The password I am reading from an encrypted credentials file with an inline msbuild task which also decrypts the password. This works perfectly, except in some cases where the password contains (or starts in my case) with a characters like T%. In such a case, msdeploy creates the application pool with an invalid password.
If I use msdeploy with the same commandline directly on from the windows prompt (and not called by msbuild), it works perfectly, even with passwords containing this characters. So I am bit screwed here.
Some expert advice is highly appreciated.
Juerg
↧