blocks|key|2863148|text|在这种情况下，您需要指定MSBuild属性VisualStudioVersion=11.0。我刚刚在http://sedodream.com/2012/08/19/VisualStudioProjectCompatabilityAndVisualStudioVersion.aspx上写了这个博客，为了你的方便，我也把它贴在下面了。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2863149|Visual+Studio2012最需要的功能之一是能够在VS2012和VS2010中打开项目(需要VS2010+SP1)。如果你还没有听说我们确实实现了这个特性。你可能想知道我们是如何做到这一点的，这可能会对你产生怎样的影响。|2863150|如果您打开在VS2010中创建的Web+Project的.csproj/.vbproj，您将看到以下导入语句。|2863151|<Import+Project="$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\
++++++++++++++++++v10.0\WebApplications\Microsoft.WebApplication.targets"+/>|code-block|syntax|javascript|2863152|当您在VS2012中打开此项目时，会对您的项目文件进行一些更改，以确保它可以在VS2010+SP1和VS2012中打开。在VS2012中第一次加载项目时，对项目所做的更改之一是添加以下内容来替换导入语句。|2863153|<PropertyGroup>
++<VisualStudioVersion+Condition="'$(VisualStudioVersion)'+==+''">10.0</VisualStudioVersion>
++<VSToolsPath+Condition="'$(VSToolsPath)'+==+''">
++++$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v$(VisualStudioVersion)</VSToolsPath>
</PropertyGroup>
<Import+Project="$(VSToolsPath)\WebApplications\Microsoft.WebApplication.targets"+Condition="'$(VSToolsPath)'+!=+''"+/>|2863154|我们删除了硬编码的10.0，取而代之的是VisualStudioVersion属性。在Visual+Studio+2012中构建时，该值始终为11.0，但对于VS+2010，该值并不存在。这就是为什么我们将其默认为10.0以上。在某些情况下，从命令行生成需要显式设置此属性。在我们开始之前，让我先解释一下这个属性是如何设置的(按这个顺序)|2863155|2863156|如果将VisualStudioVersion定义为环境变量/全局MSBuild属性，则使用该属性。|ordered-list-item|2863157|这就是VS和VS+developer命令提示符设置此value|unordered-list-item|2863158|2863159|的方式|2863160|​|2863161|2863162|基于.sln文件的文件格式版本(使用的工具集为-1\f25+sln+file+format+-1\f6)-1\f25|2863163|-1\f6为简化此语句，将创建.sln+VisualStudioVersion的VS版本的值指定为.sln+-1\f25+VS-1\f6版本的值，从而构建.sln文件|2863164|2863165|2863166|2863167|如果VS+2010是installed|2863168|Highest-versioned子工具集版本installed|2863169|
，则|2863170|选择default+|2863171|10.0|2863172|2863173|2863174|2863175|对于#2，当您构建.sln文件时，VisualStudioVersion的值将是.sln文件中找到的格式版本的-1。这里需要注意的重要一点是，如果构建一个.sln文件，它将使用与创建.sln文件的VS版本相对应的VisualStudioVersion值进行构建。因此，如果您在VS2012中创建一个.sln文件，并且总是构建该.sln文件，则VisualStudioVersion的值将为11.0。在许多情况下，如果您构建了.sln文件，您就很好。|2863176|如果您正在构建.csproj/.vbproj文件，是否需要通过.sln文件？如果您从命令行(而不是开发人员提示符)构建web项目，则VisualStudioVersion+used的值将为10.0。这是我上面展示的属性的产物。在这种情况下，您应该将其作为MSBuild属性传入。例如|2863177|msbuild.exe+MyAwesomeWeb.csproj+/p:VisualStudioVersion=11.0|2863178|在本例中，我显式地传入了属性。这将始终覆盖任何其他机制来确定VisualStudioVersion的值。如果在构建脚本中使用MSBuild任务，则可以在Properties属性或AdditionalProperties属性中指定该属性。请参阅我上一篇关于属性和AdditionalProperties之间的区别的博客文章。|2863179|如果您在构建/发布时遇到任何奇怪的行为，并且注意到导入了错误的.targets文件，那么您可能需要指定此属性。|2863180|entityMap|0|LINK|mutability|MUTABLE|url|http://sedodream.com/2012/08/19/VisualStudioProjectCompatabilityAndVisualStudioVersion.aspx^0|1E|2J|0|0|0|0|0|0|0|0|0|1|1|0|0|0|0|1|1|0|0|0|0|0|0|1|1|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|27|8|@]|9|@$A|28|B|29|1|2A]]|C|$]]|$1|D|3|E|5|6|7|2B|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|2C|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|2D|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|2E|8|@]|9|@]|C|$]]|$1|O|3|P|5|J|7|2F|8|@]|9|@]|C|$K|L]]|$1|Q|3|R|5|6|7|2G|8|@]|9|@]|C|$]]|$1|S|3|-4|5|6|7|2H|8|@]|9|@]|C|$]]|$1|T|3|U|5|V|7|2I|8|@]|9|@]|C|$]]|$1|W|3|X|5|Y|7|2J|8|@]|9|@]|C|$]]|$1|Z|3|-4|5|6|7|2K|8|@]|9|@]|C|$]]|$1|10|3|11|5|6|7|2L|8|@]|9|@]|C|$]]|$1|12|3|13|5|6|7|2M|8|@]|9|@]|C|$]]|$1|14|3|-4|5|6|7|2N|8|@]|9|@]|C|$]]|$1|15|3|16|5|V|7|2O|8|@]|9|@]|C|$]]|$1|17|3|18|5|Y|7|2P|8|@]|9|@]|C|$]]|$1|19|3|-4|5|6|7|2Q|8|@]|9|@]|C|$]]|$1|1A|3|-4|5|6|7|2R|8|@]|9|@]|C|$]]|$1|1B|3|13|5|6|7|2S|8|@]|9|@]|C|$]]|$1|1C|3|1D|5|6|7|2T|8|@]|9|@]|C|$]]|$1|1E|3|1F|5|Y|7|2U|8|@]|9|@]|C|$]]|$1|1G|3|1H|5|6|7|2V|8|@]|9|@]|C|$]]|$1|1I|3|1J|5|V|7|2W|8|@]|9|@]|C|$]]|$1|1K|3|1L|5|Y|7|2X|8|@]|9|@]|C|$]]|$1|1M|3|-4|5|6|7|2Y|8|@]|9|@]|C|$]]|$1|1N|3|-4|5|6|7|2Z|8|@]|9|@]|C|$]]|$1|1O|3|13|5|6|7|30|8|@]|9|@]|C|$]]|$1|1P|3|1Q|5|6|7|31|8|@]|9|@]|C|$]]|$1|1R|3|1S|5|6|7|32|8|@]|9|@]|C|$]]|$1|1T|3|1U|5|J|7|33|8|@]|9|@]|C|$K|L]]|$1|1V|3|1W|5|6|7|34|8|@]|9|@]|C|$]]|$1|1X|3|1Y|5|6|7|35|8|@]|9|@]|C|$]]|$1|1Z|3|-4|5|6|7|36|8|@]|9|@]|C|$]]]|20|$21|$5|22|23|24|C|$25|26]]]]

In this case you will need to specify the MSBuild property VisualStudioVersion=11.0. I just blogged about this at <a href="http://sedodream.com/2012/08/19/VisualStudioProjectCompatabilityAndVisualStudioVersion.aspx" rel="noreferrer">http://sedodream.com/2012/08/19/VisualStudioProjectCompatabilityAndVisualStudioVersion.aspx</a>, I've pasted it below as well for your convenience.

One of the most requested features of Visual Studio 2012 was the ability to open projects in both VS 2012 as well as VS 2010 (requires VS 2010 SP1). In case you haven’t heard we did implement that feature. You may be wondering how we were able to do this and how this may impact you.

If you open the .csproj/.vbproj for a Web Project created in VS2010 you will see the following import statement.

<pre><code>&lt;Import Project="$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\
 v10.0\WebApplications\Microsoft.WebApplication.targets" /&gt;
</code></pre>

When you open this project in VS 2012 there are a few changes made to your project file to ensure that it can be opened in both VS 2010 SP1 and VS 2012. One of the changes made to the project when it is first loaded in VS 2012 is to add the following to replace that import statement.

<pre><code>&lt;PropertyGroup&gt;
 &lt;VisualStudioVersion Condition="'$(VisualStudioVersion)' == ''"&gt;10.0&lt;/VisualStudioVersion&gt;
 &lt;VSToolsPath Condition="'$(VSToolsPath)' == ''"&gt;
 $(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v$(VisualStudioVersion)&lt;/VSToolsPath&gt;
&lt;/PropertyGroup&gt;
&lt;Import Project="$(VSToolsPath)\WebApplications\Microsoft.WebApplication.targets" Condition="'$(VSToolsPath)' != ''" /&gt;
</code></pre>

We removed the hard-coded 10.0 and instead used the property VisualStudioVersion. When building in Visual Studio 2012 this value will always be 11.0, but for VS 2010 it doesn’t exist. That is why we defaulted it to 10.0 above.
There are some scenarios where building from the command line will require to set this property explicitly. Before we get there let me explain how this property gets set (in this order)

<ol>
<li>If VisualStudioVersion is defined as an environment variable/global MSBuild property, that is used.

<ul>
<li>This is how VS and the VS developer command prompt set this value</li>
</ul></li>
<li>Based on the file format version of the .sln file (toolset used is sln file format –1)

<ul>
<li>To simplify this statement, the .sln file will build with specifying VisualStudioVersion to the value of the version of VS which created the .sln file.</li>
</ul></li>
<li>Choose default

<ul>
<li>10.0 if VS 2010 is installed</li>
<li>Highest-versioned sub-toolset version installed</li>
</ul></li>
</ol>

For #2 when you are building a .sln file the value of VisualStudioVersion will be –1 of the Format Version found in the .sln file. The important thing to note here is that if you build a .sln file it will build with the value of VisualStudioVersion corresponding to the version of VS which created the .sln file. So if you create a .sln file in VS2012 and you always build that .sln file the value for VisualStudioVersion will be 11.0. In many cases if you build the .sln file you are good. 

If you are building .csproj/.vbproj files w/o going through a .sln file? If you build a web project from the command line (not the developer prompt) then the value for VisualStudioVersion used will be 10.0. That is an artifact of the properties which I showed above. In this case you should pass this in as an MSBuild property. For example

<pre><code>msbuild.exe MyAwesomeWeb.csproj /p:VisualStudioVersion=11.0
</code></pre>

In this case I’m passing in the property explicitly. This will always override any other mechanism to determine the value for VisualStudioVersion. If you are using the MSBuild task in a build script, then you can specify the property either in the Properties attribute or the AdditionalProperties attribute. See my previous blog post on the difference between Properties and AdditionalProperties. 

If you encounter any funny behavior when building/publishing and you notice that the wrong .targets files are being imported then you may need to specify this property.

blocks|key|213952|text|来自this+link。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|213953|“在文本编辑器中打开*.csproj或*.vbproj+web项目文件，然后添加以下行。|213954|<IgnoreDeployManagedRuntimeVersion>True</IgnoreDeployManagedRuntimeVersion>+|code-block|syntax|javascript|213955|我在行之前添加了这行|213956|<TargetFrameworkVersion>v4.5</TargetFrameworkVersion>|213957|而且它的部署没有错误。“|213958|这对我很管用。|213959|entityMap|0|LINK|mutability|MUTABLE|url|http://social.msdn.microsoft.com/Forums/en-US/msbuild/thread/72e42de2-9e11-4ad2-bed6-ea90a72694fe^0|2|9|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@$A|11|B|12|1|13]]|C|$]]|$1|D|3|E|5|6|7|14|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|15|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|16|8|@]|9|@]|C|$]]|$1|M|3|N|5|H|7|17|8|@]|9|@]|C|$I|J]]|$1|O|3|P|5|6|7|18|8|@]|9|@]|C|$]]|$1|Q|3|R|5|6|7|19|8|@]|9|@]|C|$]]|$1|S|3|-4|5|6|7|1A|8|@]|9|@]|C|$]]]|T|$U|$5|V|W|X|C|$Y|Z]]]]

from <a href="http://social.msdn.microsoft.com/Forums/en-US/msbuild/thread/72e42de2-9e11-4ad2-bed6-ea90a72694fe">this link</a>.

"Open your *.csproj or *.vbproj web project file in a text editor and add the following line.

<pre><code>&lt;IgnoreDeployManagedRuntimeVersion&gt;True&lt;/IgnoreDeployManagedRuntimeVersion&gt; 
</code></pre>

I added the line just before the line

<pre><code>&lt;TargetFrameworkVersion&gt;v4.5&lt;/TargetFrameworkVersion&gt;
</code></pre>

and it deploys without error."

It worked for me.

blocks|key|2863234|text|我观察到，当我使用VS2012发布Web+Deploy包特性时，它会生成一个.zip文件。在压缩包中有一个名为archive.xml的文件，其中包含一个属性为‘managedRuntimeVersion=“V4.0’的createApp标记。当我使用msdeploy.exe将其同步到iis实例时，它可以正常工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2863235|然而，当我使用msbuild.exe创建一个web包.zip文件时，它包含一个带有'managedRuntimeVersion="v4.5"‘的archive.xml。尝试使用msdeploy.exe将此web包部署到IIS时会导致ERROR_APPPOOL_VERSION_MISMATCH错误。|2863236|正如赛义德·易卜拉欣·哈希米在这里解释的那样，将"/p:VisualStudioVersion=11.0“添加到我的msbuild.exe命令行有效地强制在结果web包的archive.xml中使用”managedRuntimeVersion=“v4.0”“，因此它解决了这个问题。|2863237|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I observed that when I use VS2012 Publish Web Deploy Package feature, it generates a .zip file. Inside that zip there is a file called archive.xml that contains a createApp tag with the attribute 'managedRuntimeVersion="v4.0"' . When I use msdeploy.exe to sync it to an iis instance, it works.

However, when I use msbuild.exe to create a web package .zip file, it contains an archive.xml that has 'managedRuntimeVersion="v4.5"'. Trying to deploy this web package to IIS using msdeploy.exe results in the ERROR_APPPOOL_VERSION_MISMATCH error.

As Sayed Ibrahim Hashimi explained here, adding "/p:VisualStudioVersion=11.0" to my msbuild.exe command line effectively forces 'managedRuntimeVersion="v4.0"' in the archive.xml of the resulting web package so it resolves the issue.

blocks|key|217179|text|如果有人发现这个页面在搜索为什么msdeploy/webdeploy显示类似的错误，我发现这就是解决方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|217180|要解决这个问题，只需将DeployManagedRuntimeVersion属性添加到您的VS项目中：|217181|<targetframeworkversion>v4.5</TargetFrameworkVersion></code>
<DeployManagedRuntimeVersion>v4.0</DeployManagedRuntimeVersion>|code-block|syntax|javascript|217182|从这里：http://techblog.dorogin.com/2013/11/deploying-45-projects-with-webdeploy.html|offset|length|217183|entityMap|0|LINK|mutability|MUTABLE|url|http://techblog.dorogin.com/2013/11/deploying-45-projects-with-webdeploy.html^0|0|0|0|4|25|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|X|8|@]|9|@$K|Y|L|Z|1|10]]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

For anyone who found this page searching for why msdeploy/webdeploy shows a similar error, I found this to be the solution.

To fix the problem just add DeployManagedRuntimeVersion property into your VS-project:

<pre><code>&lt;targetframeworkversion&gt;v4.5&lt;/TargetFrameworkVersion&gt;&lt;/code&gt;
&lt;DeployManagedRuntimeVersion&gt;v4.0&lt;/DeployManagedRuntimeVersion&gt;
</code></pre>

From here:
<a href="http://techblog.dorogin.com/2013/11/deploying-45-projects-with-webdeploy.html" rel="nofollow">http://techblog.dorogin.com/2013/11/deploying-45-projects-with-webdeploy.html</a>

blocks|key|213987|text|在我的例子中，构建服务器上没有安装WebDeploy。所以它抛出了一个类似的错误。我安装了WebDeploy，我是金子。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|213988|http://www.microsoft.com/en-ca/download/confirmation.aspx?id=25230|offset|length|213989|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1U|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

In my case WebDeploy was not installed on the build server. So it threw a similar error. I installed WebDeploy and I was golden.

<a href="http://www.microsoft.com/en-ca/download/confirmation.aspx?id=25230" rel="nofollow">http://www.microsoft.com/en-ca/download/confirmation.aspx?id=25230</a>

We recently upgraded our VS 2010 and .NET 4 application to VS 2012 and .NET 4.5. We have a build script to deploy the application on the test server. We have two boxes - one is Windows 8 with VS 2012 (fresh install) and other is Windows 7 with VS 2010 and VS 2012 (installed newly). 

When running the build script from Windows 8 box build script is working well and deploys the application to test server. But when deploying the application from Windows 7 box I get the following error:

<blockquote>
 "C:\Achinth\Build\Work\build\qa1sb.proj" (DeployAll target) (1) ->"C:\Achinth\Build\Work\App\App.csproj" (ResolveReferences;MsDeployPublish target) (2) ->(MSDeployPublish target) -> C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\Web\Microsoft.Web.Publishing.targets(3847,5): error : Web deployment task failed.((8/19/2012 6:23:41 PM) An error occurred when the request was processed on the remote computer.) [C:\Achinth\Build\Work\App\App.csproj]C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\Web\Microsoft.Web.Publishing.targets(3847,5): error : \r [C:\Achinth\Build\Work\App\App.csproj]C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\Web\Microsoft.Web.Publishing.targets(3847,5): error : (8/19/2012 6:23:41 PM) An error occurred when the request was processed on the remote computer.\r [C:\Achinth\Build\Work\App\App.csproj]C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\Web\Microsoft.Web.Publishing.targets(3847,5): error : The application pool that you are trying to use has the 'managedRuntimeVersion' property set to 'v4.0'. This application requires 'v4.5'. [C:\Achinth\Build\Work\App\App.csproj]
</blockquote>

Looking at the error it looks like that MSBuild is using VS 2010 targets instead of VS 2012, which is causing the error. Since Windows 8 box does not have VS 2010 it is using VS 2012 targets correctly.

Can some one please provide pointers on how to make MSBuild to pick the right version?

MSBuild deploy failing after upgrade to .NET 4.5

Visual Studio

测试服务

服务器

Windows

我们最近将VS 2010和.NET 4应用程序升级到了VS 2012和.NET 4.5。我们有一个构建脚本来在测试服务器上部署应用程序。我们有两个盒子-一个是Windows 8，VS 2012 (全新安装)，另一个是Windows 7，VS 2010和VS 2012 (新安装)。当从Windows8运行构建脚本时，构建...

问升级到.NET 4.5后MSBuild deploy失败
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问升级到.NET 4.5后MSBuild deploy失败EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问升级到.NET 4.5后MSBuild deploy失败
EN