msdeploy v2 不适用于 vs2010 的软件包
我安装了 v1 的 msdeploy，然后将其卸载以安装 v2。 现在，当我运行deploy.cmd时，我的vs2010包会失败，因为它找不到注册表项 - 即使我已经创建了一个指向v2路径的MSDeployPath环境变量？
我在“我的电脑/属性”下的“高级系统设置/环境变量”中将 MSDeployPath 设置为“C:\Program Files\IIS\Microsoft Web Deploy V2”。
当我运行VS2010的deploy.cmd文件时出现的错误是： Files\IIS\Microsoft这时候出乎意料。
有人知道如何解决这个问题吗？ vs2010包的deploy.cmd在注册表中查找/1。
那么如果路径变量不起作用，我该如何更改它以查找 /2
I had v1 of msdeploy installed and I uninstalled it to install the v2.
Now my vs2010 packages fail when I run the deploy.cmd because it can't find the registry entry - even though I've created an MSDeployPath environment variable pointing to the v2 path?
I have MSDeployPath set to "C:\Program Files\IIS\Microsoft Web Deploy V2" in the Advanced System Settings/Environment Variables under My Computer/Properties.
The error I get when I run the VS2010 deploy.cmd file is:
Files\IIS\Microsoft was unexpected at this time.
Anyone know how to fix this? The vs2010 package's deploy.cmd looks for /1 in the registry.
So how do I change this to look for /2 if the path variable doesn't work
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
编辑 .cmd 文件以查找正确的注册表路径。 /2 而不是 /1。
我的理解是 TFS 2010 sp1 修复了这个问题。
SP1 之前版本的 cmd 文件中的行如下所示：
SP1 后它看起来像这样
Edit the .cmd file to look for the correct registry path. /2 instead of /1.
My understanding is that TFS 2010 sp1 fixes this.
The line from the cmd file for pre SP1 builds looks like this:
post SP1 it looks like this
当我尝试使用 MSbuild 创建的包下的 Bath 文件部署网站时，我也遇到了同样的问题。唯一的区别是我是远程执行的。也就是说，我将该任务分配给我的构建服务器，一旦构建成功，它就会执行命令
虽然设置参数 xml 可用，但它抱怨它是意外的。通常它表示远程Web 部署我们不需要管理员权限。（在我的情况下，构建服务器在没有管理员权限的情况下运行）。然后我远程登录到构建服务器计算机，然后使用命令行尝试手动部署。但最终得到相同的结果问题。然后我尝试的只是将包复制到桌面，然后进行远程部署。已成功将文件传输到目标 IIS 位置。
构建服务器尝试部署的位置：C:\Program Files (x86)\Jenkins\jobs\Exile-LibrarySystem\workspace\Exile-LibrarySystem\Exile-LibrarySystem\obj\Staging\Package
I认为由于该文件夹的访问权限受到限制，因此无法执行该操作。否则，当我尝试在构建服务器计算机的桌面中进行部署时，我应该会遇到相同的问题。有什么解决办法可以在构建服务器位置完成此部署工作吗？
谢谢
I also get the same issue when I am trying to deploy the web site using bath file under the package created by MSbuild. Only difference is I am doing it remotely.that is I assign that task to my build server and once a build is successful then it execute the command
Although the set parameter xml is available it complains the it is unexpected.Normally it says for a remote web deployment we dont need admin privileges.(In my case build server is running with out admin privileges).Then I remotely logged to the build server machine and then using a command line try to to the deployment manually.But end up with the same issue.Then what I try was just copy the package in to a desktop and then did the remote deployment.It was successfully transferred the files into target IIS location.
Location where build server tries to to the deployment : C:\Program Files (x86)\Jenkins\jobs\Exile-LibrarySystem\workspace\Exile-LibrarySystem\Exile-LibrarySystem\obj\Staging\Package
I think since this folder has limits access it cant do the operation.Otherwise I should have end up with the same issue when I was trying to do the deployment in the desktop in build server machine. Is there any work around where I can get this deployment job done with in the build server location ?
Thanks