尝试使用Azure Key Vault,但是在TFS中运行migration.exe时失败 [英] Trying to use Azure Key Vault but fails when migrate.exe is run in TFS

查看:126
本文介绍了尝试使用Azure Key Vault,但是在TFS中运行migration.exe时失败的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们正在尝试将Azure密钥保管库用于始终加密的列.我已经在本地计算机上设置并运行了所有代码,但是当我尝试通过TFS进行部署时,当Migrate.exe运行CF并点击seed方法时,它将失败.我已经尝试了一切 我知道强制绑定,卸载并重新安装.任何帮助将不胜感激!

We are trying to use Azure key vault for always encrypted columns. I have the code all setup and running perfectly on my local machine but when I try and deploy through TFS it fails when Migrate.exe runs the CF and hits the seed method. I have tried everything I know to force binding, uninstall and reinstall. Any help would be greatly appreciated!

TFS部署日志

2018-11-04T23:30:56.1072858Z ## [section]开始:使用CF更新数据库

推荐答案

是否可以将System.Net.Http二进制文件(4.2.0.0)复制到与应用程序相同的文件夹中,然后构建并尝试运行.如果没有自动生成绑定重定向,请手动添加它以解决此问题(理想情况下,它将自动生成).

Can you copy the System.Net.Http binary(4.2.0.0) in the same folder as your application, build and try to run. If binding redirects are not generated automatically then add it manually to fix this issue (ideally it will be generated automatically).

<dependentAssembly>   

< assemblyIdentity name ="System.Net.Http" publicKeyToken ="b03f5f7f11d50a3a"文化=中立" />  

<assemblyIdentity name="System.Net.Http" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />   

< bindingRedirect oldVersion ="0.0.0.0-4.2.0.0" newVersion ="4.2.0.0" />  </dependentAssembly>

<bindingRedirect oldVersion="0.0.0.0-4.2.0.0" newVersion="4.2.0.0" />  </dependentAssembly>


这篇关于尝试使用Azure Key Vault,但是在TFS中运行migration.exe时失败的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆