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.
我有cruisecontrol.net构建一个asp.net Web部署项目。这很有效,直到我创建了多个部署“配置”。基本上我们有开发,测试,阶段和产品。
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.
stage和prod配置有一个web.config替换设置,用于将纯文本连接字符串部分更改为我们的生产Web服务器用作加密值的部分。
The problem is after the build the resulting web.config has a different CipherValue that what was in our source control repository.
问题是在构建之后,生成的web.config具有与源代码控制存储库中不同的CipherValue。
Is msbuild re-encrypting the connection strings during the build?
msbuild是否在构建期间重新加密连接字符串?
Paul
1 个解决方案
#1
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.
如果您使用的是此MSDN文章中描述的系统,那么如果在另一台计算机上生成CipherValue,则它将有所不同。但是它们也只能在该构建服务器上使用。
#1
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.
如果您使用的是此MSDN文章中描述的系统,那么如果在另一台计算机上生成CipherValue,则它将有所不同。但是它们也只能在该构建服务器上使用。