Web Deployment Project with an replacement .config geting "changed"

I have cruisecontrol.net building a asp.net web deployment project. This is working great until i created multiple deployment "configurations". Basically we have a dev,test,stage, and prod.

The stage and prod configurations have a web.config replacement setup to change the plain text connectionstring section to what our production webservers use as the encrypted value.

The problem is after the build the resulting web.config has a different CipherValue that what was in our source control repository.

Is msbuild re-encrypting the connection strings during the build?

Paul

From stackoverflow

• If you are using the system described in this MSDN article, then the CipherValue will be different if it is generated on a different machine. But then they would also only be usable on that build server.